There is a flag variable in about:config 'app.update.updatesAvailable' that gets set to true. The notification would have gone away on its own in about a day when Firefox checked for updates.
Because in its default setting only update.mozilla.org and addons.mozilla.org are the only sites on the whitelist. Every other site gives you a little yellow bar saying that the install of an extension was blocked. You need to enable the site and refresh the page before you can install the extension.
There was a server side change that prevents the exploit from working on UMO. You only need to be concerned with sites on your install software whitelist.
By default, if you enter a search term in the address field and press Enter, a Google "I'm Feeling Lucky" search is performed, and you're taken to the first result of that search directly. If you prefer to see the standard search result list instead, add the following code to your user.js file:
// Change to normal Google search:
user_pref("keyword.URL", "http://www.google.com/search?btnG=Google+Search&q =");
Of course, you could also change to a completely different search engine by changing the string to something else. The default search string is: "http://www.google.com/search?btnI=I%27m+Feeling+L ucky&q=".
There's been lots of speculation about which browser will get Acid2 working first. I'd put my money on Safari. The problem is that we're late in the Gecko 1.8/Firefox 1.1 release cycle and there are a couple of bugs that would be quite a lot of work to fix, and introduce significant risk, and they're just not as important as other work that we have long planned for 1.8 and some other strategic work that I'll blog about soon. We will get to it in 1.9.
I'm sure some will seize on this as an opportunity to say "Gecko developers don't care about standards"... they're simply wrong, as anyone can tell by looking at the huge number of standards compliance bugs we fix in every release. And keep in mind that if everyone's #1 priority was always standards compliance, Firefox would never have happened. -Roc
The next release of Mozilla (it won't be called Mozilla) will get any features that are Core bugs. The cached back and forward feature is a Core change. Sanatize is not.
bugzilla.mozilla.org/show_bug.cgi?id=131456 Memory use does not go down after closing tabs (resources not released) Resolved:Fixed
One of the many core changes that are going to be in Fx 1.1.
Slashdot Mirror
Middle click won't ever work on a 1.0.x release. You will need to wait until the 1.1 release. It was fix on the trunk by bug 151249.
bugzilla.mozilla.org/show_bug.cgi?id=151249
There is a flag variable in about:config 'app.update.updatesAvailable' that gets set to true. The notification would have gone away on its own in about a day when Firefox checked for updates.
Because in its default setting only update.mozilla.org and addons.mozilla.org are the only sites on the whitelist. Every other site gives you a little yellow bar saying that the install of an extension was blocked. You need to enable the site and refresh the page before you can install the extension.
There was a server side change that prevents the exploit from working on UMO. You only need to be concerned with sites on your install software whitelist.
There was a server side change that prevents the exploit from working on UMO. Now you need to be careful of the sites you whitelist. Also see the post by alanjstr http://it.slashdot.org/comments.pl?sid=148775&cid= 12467737
The exploit has been largely nullified by implementing a server side change.
The exploit would still work if you whitelist the wrong site.
Change the search mode in the address field
By default, if you enter a search term in the address field and press Enter, a Google "I'm Feeling Lucky" search is performed, and you're taken to the first result of that search directly. If you prefer to see the standard search result list instead, add the following code to your user.js file:
// Change to normal Google search:q =");
user_pref("keyword.URL", "http://www.google.com/search?btnG=Google+Search&
Of course, you could also change to a completely different search engine by changing the string to something else. The default search string is: "http://www.google.com/search?btnI=I%27m+Feeling+L ucky&q=".
http://kb.mozillazine.org/ActiveX "Mozilla does not support ActiveX controls natively. However, a plugin for ActiveX controls support is available"...
http://weblogs.mozillazine.org/roc/archives/2005/0 4/acid2.html
... they're simply wrong, as anyone can tell by looking at the huge number of standards compliance bugs we fix in every release. And keep in mind that if everyone's #1 priority was always standards compliance, Firefox would never have happened. -Roc
There's been lots of speculation about which browser will get Acid2 working first. I'd put my money on Safari. The problem is that we're late in the Gecko 1.8/Firefox 1.1 release cycle and there are a couple of bugs that would be quite a lot of work to fix, and introduce significant risk, and they're just not as important as other work that we have long planned for 1.8 and some other strategic work that I'll blog about soon. We will get to it in 1.9.
I'm sure some will seize on this as an opportunity to say "Gecko developers don't care about standards"
Part 2
Use about:config to modify browser.download.manager.showAlertOnComplete
http://mozillazine.org/misc/about:config/
Well For Firefox this will solve your issue http://kb.mozillazine.org/Emacs_Keybindings_(Firef ox)
The next release of Mozilla (it won't be called Mozilla) will get any features that are Core bugs. The cached back and forward feature is a Core change. Sanatize is not.
See the Seamonkey homepage for more info.bugzilla.mozilla.org/show_bug.cgi?id=131456 Memory use does not go down after closing tabs (resources not released) Resolved:Fixed One of the many core changes that are going to be in Fx 1.1.
bugzilla.mozilla.org/show_bug.cgi?id=131456 Memory use does not go down after closing tabs (resources not released) - Resolved:Fixed
Opera did not have it before, see my comment in this article. Cliffnotes: SVG work on Mozilla dates back to at least 2000 and Official builds of Mozilla 1.0 w/ SVG were available in 2002.7 981&cid=12399773
http://developers.slashdot.org/comments.pl?sid=14
SVG has been a compile time option since at least 2000. See the beginnings of netscape.public.mozilla.svg
Heck Mozilla 1.0 had SVG support with these Official builds.mozilla-i686-pc-linux-gnu-svg-RH7.1.tar.gz 06-Jun-2002 19:46
mozilla-win32-svg-mathml-1.0.zip 07-Jun-2002 13:38