Be careful what you ask for. Slashdot might use the "Power Ranger" from a recent version of the opera.com web site as the icon representing the browser.
Breakpad doesn't have anything to do with crash recovery other than including a "Relaunch Firefox" button. Firefox's session restoration is a separate thing.
Furthermore, for those of you with notebooks/WiFi -- for God's sake, turn off Automatically check for Updates to: Firefox, Installed Add-Ons and Search Engines from the 'Updates' tab in the 'Advanced' options, especially if you're going to be spending time in a coffee bar.
Updates to Firefox itself are safe even over WiFi. Updates to extensions you got from addons.mozilla.org are also safe. Turning off automatic updates will make you less secure, not more.
That also turns off the "Did you mean:" spelling suggestions, the image results when you search for something like "Firefox logo", and the map results when you search for something like a zip code or address. If you found a "full Google search" without ads, that would be more interesting.
I'm not sure what you mean by "bad profile support", but graphics and use of Mac OS X APIs are getting better every week on trunk. You might consider trying out a recent Firefox 3 alpha.
Can you name some Firefox features (in Firefox 2 or planned for Firefox 3) that you think should be left for add-ons? (e.g. because most Firefox users won't need them and they add significantly to download size or startup time or page-load time.)
What app are you copying from and what app are you copying to? How will I be able to tell that something is wrong -- what do I do in the receiving app that will feel buggy?
It's possible to turn off the back-forward cache by setting browser.sessionhistory.max_viewers to 0 in about:config. That said, for some users, Firefox uses a lot of memory due to actual leaks rather than this kind of caching.
Re:redraws involve headache-inducing white flashes
on
Gran Paradiso Alpha 3
·
· Score: 1
I think this is bug 361600. I agree that it's annoying, and it looks like it will be fixed in time for Firefox 3.
Since it contains a lot of changes to Gecko but very few changes to the Firefox UI, I think it makes more sense to call it a "Gecko 1.9 alpha" than a "Firefox 3 alpha".
It's ok if the nose is a pixel offset from the reference-rendering position. IIRC, it depends on the order in which borders are drawn, which isn't specified by CSS. It's even ok, and considered ideal by some, if the nose is anti-aliased to be "half a pixel offset" from the reference-rendering position.
Slashdot Mirror
Be careful what you ask for. Slashdot might use the "Power Ranger" from a recent version of the opera.com web site as the icon representing the browser.
Interestingly, the Safari beta seems to be the second ACID2-compliant browser for Windows (after Opera). Nicely done, Apple!
:)
Firefox 3 alpha 5 also passes ACID2, and IMO the Firefox "alpha" is more stable than the Safari "beta". I guess we'll see who releases first
Breakpad doesn't have anything to do with crash recovery other than including a "Relaunch Firefox" button. Firefox's session restoration is a separate thing.
Actually, you do have that guarantee, thanks to https.
Nuclear fission power is also "second-hand" fusion power. The uranium we use in fission plants comes from supernova explosions.
Furthermore, for those of you with notebooks/WiFi -- for God's sake, turn off Automatically check for Updates to: Firefox, Installed Add-Ons and Search Engines from the 'Updates' tab in the 'Advanced' options, especially if you're going to be spending time in a coffee bar.
Updates to Firefox itself are safe even over WiFi. Updates to extensions you got from addons.mozilla.org are also safe. Turning off automatic updates will make you less secure, not more.
If it's valid behavior according to the protocol, and it's faster, and it's not bad nettiquette, then why, pray tell, isn't it on by default?
Because some servers violate the protocol by responding incorrectly to pipelined requests. At least, that was the reason 2 years ago.
That also turns off the "Did you mean:" spelling suggestions, the image results when you search for something like "Firefox logo", and the map results when you search for something like a zip code or address. If you found a "full Google search" without ads, that would be more interesting.
The bfcache limit is a global number of pages, not a per-tab number of pages.
I'm not sure what you mean by "bad profile support", but graphics and use of Mac OS X APIs are getting better every week on trunk. You might consider trying out a recent Firefox 3 alpha.
Can you name some Firefox features (in Firefox 2 or planned for Firefox 3) that you think should be left for add-ons? (e.g. because most Firefox users won't need them and they add significantly to download size or startup time or page-load time.)
Why would targeted ads be more annoying than untargeted ads?
On your flying bicycle?
Static typing is great, but why do you want the code to be compiled on the server rather than on the client?
in the case of U on my mac, to the first bookmark starting with W
That is... impressive. Do you know whether there's a bug filed?
Use adblock, save the planet?
What app are you copying from and what app are you copying to? How will I be able to tell that something is wrong -- what do I do in the receiving app that will feel buggy?
I've found the same thing with the tray tables. But have you tried putting your lap top on top of your lap?
The storage and offline APIs are part of Gecko, so they'll be in Galeon too.
Yeah. For a solid percentage of the 6-digit numbers, Google will give you a Debian bug report, a Gnome bug report, or a Mozilla bug report.
It's possible to turn off the back-forward cache by setting browser.sessionhistory.max_viewers to 0 in about:config. That said, for some users, Firefox uses a lot of memory due to actual leaks rather than this kind of caching.
I think this is bug 361600. I agree that it's annoying, and it looks like it will be fixed in time for Firefox 3.
;)
It's even more annoying in debug builds
Since it contains a lot of changes to Gecko but very few changes to the Firefox UI, I think it makes more sense to call it a "Gecko 1.9 alpha" than a "Firefox 3 alpha".
It's ok if the nose is a pixel offset from the reference-rendering position. IIRC, it depends on the order in which borders are drawn, which isn't specified by CSS. It's even ok, and considered ideal by some, if the nose is anti-aliased to be "half a pixel offset" from the reference-rendering position.
Don't Google "How to waste time at work" before reading Slashdot.