in late 2006. So this has been in the works for almost 2 years. Considering that Google kept Chrome under wraps fairly well, this is not a great example of competition driving the market.
CAcert has not asked for inclusion. Bug 215243 was opened by a Mozilla/CAcert user. The bug is currently closed as Invalid because CAcert will open a new bug when they are capable of meeting Mozilla's Certificate policy.
Comment 158 by Ian Grigg he is/was the auditor for CAcert "...In the meantime, there is no point in pressuring Mozilla on the issue. Better
if you wish to help, join CAcert as a user and contribute on their large task
list."
Comment 165 by Nicholas E. Bebout "Marking as VERIFIED, with the understanding that we (CAcert, I'm a CAcert, Inc.
member) will open a new bug when the audit is done. "
Your application uses the middle button to paste the current PRIMARY (usually the last-highlighted) selection at the pointer position, as follows:
Table 10-1 Effect of modifier keys on a middle button transfer operation
Modifier Function
Unmodified Copy selection
Ctrl Copy selection
Shift Move selection
Shift+Ctrl Create link, shortcut or alias to selection
Do not over-ride this functionality in any part of your user interface where the transfer action is likely to be useful. If you do intend to use the middle button for a different purpose somewhere, only do so as a shortcut for experienced users, and only for operations that can also be performed without using the right button or middle button.
WhatWG and W3 HTML5 working groups drastically altered the specification for such that the Mozilla implementation was non-conforming. Rather than have legacy that only worked in Fx 3 Mozilla did the only thing they could do which was to drop the feature. It will be in a later release once a standard is hashed out.
Chasing after a declining marketshare is a poor business strategy. Windows 98 and ME boxes will be replaced as the years go on.
Current security bugs often require completely different patches to fix the security flaw. The code base that was used to develop Firefox 2, Gecko 1.8, became largely static in August of 2005. This means that security patches for Firefox 2 start taking significantly more developer time as code bases diverge. The Gecko 1.8 and 1.9 have already have significant differences in the code base different graphics rendering platform, text layout and html processing just to name a few.
Firefox 3 and Gecko 1.9 will not run on any version of Windows earlier than 2000. This means that the project he suggests would need to be build off the Gecko 1.8 code base. This code base is too old for new projects to be developed on it. The last security patch on the Gecko 1.8 code base will be about a year from now. This leaves any code using this open to any security issues discovered.
The current implementation keeps bookmarks.html in sync with the sqlite bookmarks database. See Places bookmarks have landed! for details.
Most notably from that post is this tidbit.
* Migration from bookmarks.html -> places.sqlite will happen only once.
From then on, bookmarks.html will be kept up to date with changes in
the db, but not the other way around. This means that after initial
import, if you make any changes to bookmarks.html (say, by running
Firefox 2 and editing your bookmarks) you will need to manually export
them and re-import them into the bookmark-on-places nightly (see bug
381216). This means if you run Firefox 2 and Minefield or Gran Paradiso Alpha 5, when it is released, using a single profile Firefox will overwrite any changes. It is imperative for testers to know about how to use the profile manager.
NASA has been sending seeds to space for a long time. In 1989 I, and all my classmates, received packages of tomato seeds as part of LDEF Experiment P0004-01. A little bit of Googleing turned up Park Seed SEEDS project which nicely describes the project.
Most of my classmates killed their plants. I planted mine in the family garden and bore fruit. That was quite tasty. As I recall there was some legalese that said don't eat the fruit that the plants bear lest you turn into a tomato based superhero.
Gecko 1.9 will be shipped in Firefox 3, currently scheduled for the May or November 2007, depending on which part of the Mozilla Wiki to belive*. From what I understand there are plans to release a Firefox 4 off Gecko 1.9, much like Firefox 1.5 and Firefox 2 are built off Gecko 1.8. So that would put these changes in Firefox 5 time frame, yes this is quite some time away.
The bug is not Mozilla's fault and was found to be corrected by a third party patch. What do you expect Mozilla to do? Write a special section of code to detect if you are running a specific motherboard, BIOS, and provide you with a download link for the BIOS update.
If the bug I mentioned in the previous post is not your issue. Then please file a bug at Mozilla's Bugzilla and reply to this post with the bug number. Please be as specific as possible and try and follow the bug writing guidelines
Mozilla 1.0.x users will need to manually update their browser to a new major version.
Mozilla will be releasing Firefox 1.5.0.8 which contains a patch to the update system that allows Firefox 1.5 to offer an option to upgrade to Firefox 2. This upgrade will only be offered and not forced unlike the minor updates which download, install and update with little user input.
This issue was found to be an issue that was solved by upgrading you motherboard's BIOS. See bug 282392. The bug also lists a few other options besides upgrading your BIOS.
Slashdot Mirror
in late 2006. So this has been in the works for almost 2 years. Considering that Google kept Chrome under wraps fairly well, this is not a great example of competition driving the market.
err 3.1
No it is the name for the unstable trunk, Shiretoko is the code name for Firefox 3.
Mozilla's policy is set and publicly available at http://www.mozilla.org/projects/security/certs/policy/ there would not be an exception for just CAcert. The policy would need to be amended.
See my comment on one of the other CA Cert threads. Short story is that CA Cert will file a bug when they can meet the rules at http://www.mozilla.org/projects/security/certs/policy/
This is Firefox's behavior too. Once you fetch the cert the Add security exception dialog has "permanently store this exception" checked.
CAcert has not asked for inclusion. Bug 215243 was opened by a Mozilla/CAcert user. The bug is currently closed as Invalid because CAcert will open a new bug when they are capable of meeting Mozilla's Certificate policy.
Comment 158 by Ian Grigg he is/was the auditor for CAcert "...In the meantime, there is no point in pressuring Mozilla on the issue. Better if you wish to help, join CAcert as a user and contribute on their large task list."
Comment 165 by Nicholas E. Bebout "Marking as VERIFIED, with the understanding that we (CAcert, I'm a CAcert, Inc. member) will open a new bug when the audit is done. "
WMP 11 plugin for Firefox http://port25.technet.com/pages/windows-media-player-firefox-plugin-download.aspx
For current versions http://releases.mozilla.org/pub/mozilla.org/firefox/releases/ and if you really need something pre 2.0 then use ftp://ftp.mozilla.org/pub/firefox/releases/
I know a work around has been posted. But this is not some random feature that Mozilla devs came up with. It is a common interaction in unix desktops and is specified in the Gnome HIG. http://library.gnome.org/devel/hig-book/stable/input-mouse.html.en
Your application uses the middle button to paste the current PRIMARY (usually the last-highlighted) selection at the pointer position, as follows:
Table 10-1 Effect of modifier keys on a middle button transfer operation Modifier Function
Unmodified Copy selection
Ctrl Copy selection
Shift Move selection
Shift+Ctrl Create link, shortcut or alias to selection
Do not over-ride this functionality in any part of your user interface where the transfer action is likely to be useful. If you do intend to use the middle button for a different purpose somewhere, only do so as a shortcut for experienced users, and only for operations that can also be performed without using the right button or middle button.
WhatWG and W3 HTML5 working groups drastically altered the specification for such that the Mozilla implementation was non-conforming. Rather than have legacy that only worked in Fx 3 Mozilla did the only thing they could do which was to drop the feature. It will be in a later release once a standard is hashed out.
The Mozilla Foundation which owns the Corp has funded several projects in 2007.
Current work includes improving l10n tools Community Giving and Tools for the L10n Process
2006 10k USD to openbsd to continue development of openbsd and openssh. Mozilla Foundation activities, week ending 2006/03/31
Emacs keybindings for Firefox. It covers most of the common use cases.
In which case there is Minimo. The current Firefox project track does not lend it self to the suggestion made by the cnet article.
Chasing after a declining marketshare is a poor business strategy. Windows 98 and ME boxes will be replaced as the years go on.
Current security bugs often require completely different patches to fix the security flaw. The code base that was used to develop Firefox 2, Gecko 1.8, became largely static in August of 2005. This means that security patches for Firefox 2 start taking significantly more developer time as code bases diverge. The Gecko 1.8 and 1.9 have already have significant differences in the code base different graphics rendering platform, text layout and html processing just to name a few.
Firefox 3 and Gecko 1.9 will not run on any version of Windows earlier than 2000. This means that the project he suggests would need to be build off the Gecko 1.8 code base. This code base is too old for new projects to be developed on it. The last security patch on the Gecko 1.8 code base will be about a year from now. This leaves any code using this open to any security issues discovered.
The current implementation keeps bookmarks.html in sync with the sqlite bookmarks database. See Places bookmarks have landed! for details. Most notably from that post is this tidbit.
* Migration from bookmarks.html -> places.sqlite will happen only once. From then on, bookmarks.html will be kept up to date with changes in the db, but not the other way around. This means that after initial import, if you make any changes to bookmarks.html (say, by running Firefox 2 and editing your bookmarks) you will need to manually export them and re-import them into the bookmark-on-places nightly (see bug 381216). This means if you run Firefox 2 and Minefield or Gran Paradiso Alpha 5, when it is released, using a single profile Firefox will overwrite any changes. It is imperative for testers to know about how to use the profile manager.It is https://bugzilla.mozilla.org/show_bug.cgi?id=36349 6 - "gmail talk, onclick textarea creates new space in contacts list"
NASA has been sending seeds to space for a long time. In 1989 I, and all my classmates, received packages of tomato seeds as part of LDEF Experiment P0004-01. A little bit of Googleing turned up Park Seed SEEDS project which nicely describes the project. Most of my classmates killed their plants. I planted mine in the family garden and bore fruit. That was quite tasty. As I recall there was some legalese that said don't eat the fruit that the plants bear lest you turn into a tomato based superhero.
The Long Duration Exposure Facility project main page.Gecko 1.9 will be shipped in Firefox 3, currently scheduled for the May or November 2007, depending on which part of the Mozilla Wiki to belive*. From what I understand there are plans to release a Firefox 4 off Gecko 1.9, much like Firefox 1.5 and Firefox 2 are built off Gecko 1.8. So that would put these changes in Firefox 5 time frame, yes this is quite some time away.
* http://wiki.mozilla.org/Firefox3/Schedule
* http://wiki.mozilla.org/ReleaseRoadmap
You may find Bug 277547 more palatable.
Because Ubuntu has approval to use the trademark. See Chris Beard's blog post about the subject Mozilla and Ubuntu
The bug is not Mozilla's fault and was found to be corrected by a third party patch. What do you expect Mozilla to do? Write a special section of code to detect if you are running a specific motherboard, BIOS, and provide you with a download link for the BIOS update.
If the bug I mentioned in the previous post is not your issue. Then please file a bug at Mozilla's Bugzilla and reply to this post with the bug number. Please be as specific as possible and try and follow the bug writing guidelines
As I understand it Firefox 1.5 will be supported for another 6 months. As of right now I don't have a link to an official posting about that.
Mozilla 1.0.x users will need to manually update their browser to a new major version.
Mozilla will be releasing Firefox 1.5.0.8 which contains a patch to the update system that allows Firefox 1.5 to offer an option to upgrade to Firefox 2. This upgrade will only be offered and not forced unlike the minor updates which download, install and update with little user input.
Mozilla Firefox 1.5.0.8 quality assurance
Mozilla quality assurance blog
Slightly tangential Mozilla bugday info. Bugdays happen every Tuesday with three sessions a day for the different timezones
This issue was found to be an issue that was solved by upgrading you motherboard's BIOS. See bug 282392. The bug also lists a few other options besides upgrading your BIOS.