Downloading a "Definition Update" is how the phishing/malware protection works by default. However, real time checking has been possible since FF 2.0 was released. The user actually has to enable it in their preferences. I personally doubt anyone ever does.
It is even more of a non-issue with 3.0. Bug #388652 is about removing the real-time checking and it looks like it is seriously being considered.
In the list of features slated for Firefox 3.0 is a sync api to allow for these kind of things. The places apis also allows for something called remote containers. Remote containers let you implement a folder with bookmarks from a different datasource, some examples that come to mind: file system, ie favorites, del.icio.us, etc...
SQLite is developed for embedding so it is miniscule (less than 250KiB). It was already included in Firefox 2.0 so it does not add any size to Firefox 3.0. It also allows for some interesting ideas that are being played with for the new release, like site annotation and full text indexing.
It has to be that long before it can be implemented. The implementation depends on the ECMAScript 4 specification. ActionScript 3 is based off of that spec while Javascript 1.7 is based on the ECMAScript 3 spec. The reason ECMAScript 4 is so important is that it allows for strong typing of variables. That strong typing allows Tamarin to compile the script down to machine level code. If strong typing is not used then the script must be interpreted at runtime.
The big reason for using SQL as bookmark storage is that hyistory and bookmarks have been merged. A bookmark now consists as a set of annotations to a url in history.
Google's safe-browsing extension that was landed on the trunk has 2 modes. The standard mode, downloads a blacklist of sites and the sites are looked up locally. The enhanced mode, sends every URL to Google. Mozilla has not committed to either of these modes.
We are still working on goals for 2.0/3.0 and are drafting a PRD for its development. Some likely goals include:
* Improvements to Bookmarks/History * Per-Site Options * Enhancements to the Extensions system, Find Toolbar, Software Update, Search and other areas. * Accessibility compliance * More... ?
(Note: placing an item on this list does not mean it will not be complete until 2.0/3.0, rather we would like to be done by 2.0/3.0, it may be implemented by 1.5, 2.0 or 3.0)
Or you could check out the wiki for more detailed information.
Originally this was suppose to be a 1.1 release, but since there had been almost a year worth of development on the Gecko rendering engine between 1.0 and this release, they decided to bump the version to 1.5. They've also included a lot more features than originally planned for. Such as the new software update.
I'm just a lowely extension developer, but I have managed to get a couple of patches checked in. Just because you don't have CVS commit access doesn't mean they won't except your patch. Its all about chasing down bugs and then finding someone to review, super-review your work.
Those plans have morphed somewhat, but are in fact still a live. They are now called libxul or xulrunner, and I believe are part of the Mozilla 2.0 plan.
There is currently a ton of work being done on Sunbird. The backend is being rewritten to allow multiple calendar type providers, and the frontend is being cleaned up to match the new backend. Check out the calendar portion of: Mozilla Wiki for more details.
Slashdot Mirror
In certain locales Yahoo is already the default. From what I can gather Mozilla and Yahoo have a similar agreement.
Downloading a "Definition Update" is how the phishing/malware protection works by default. However, real time checking has been possible since FF 2.0 was released. The user actually has to enable it in their preferences. I personally doubt anyone ever does.
It is even more of a non-issue with 3.0. Bug #388652 is about removing the real-time checking and it looks like it is seriously being considered.
In the list of features slated for Firefox 3.0 is a sync api to allow for these kind of things. The places apis also allows for something called remote containers. Remote containers let you implement a folder with bookmarks from a different datasource, some examples that come to mind: file system, ie favorites, del.icio.us, etc...
SQLite is developed for embedding so it is miniscule (less than 250KiB). It was already included in Firefox 2.0 so it does not add any size to Firefox 3.0. It also allows for some interesting ideas that are being played with for the new release, like site annotation and full text indexing.
It has to be that long before it can be implemented. The implementation depends on the ECMAScript 4 specification. ActionScript 3 is based off of that spec while Javascript 1.7 is based on the ECMAScript 3 spec. The reason ECMAScript 4 is so important is that it allows for strong typing of variables. That strong typing allows Tamarin to compile the script down to machine level code. If strong typing is not used then the script must be interpreted at runtime.
Isn't that what Web Hypertext Application Technology Working Group is?
The big reason for using SQL as bookmark storage is that hyistory and bookmarks have been merged. A bookmark now consists as a set of annotations to a url in history.
Google's safe-browsing extension that was landed on the trunk has 2 modes. The standard mode, downloads a blacklist of sites and the sites are looked up locally. The enhanced mode, sends every URL to Google. Mozilla has not committed to either of these modes.
Check out the developers wiki on this plan. Although I beleive you will only be able to use other languages from within chrome.
See this mozillazine article. The counter doesn't include downloads from the software update system.
Originally this was suppose to be a 1.1 release, but since there had been almost a year worth of development on the Gecko rendering engine between 1.0 and this release, they decided to bump the version to 1.5. They've also included a lot more features than originally planned for. Such as the new software update.
I'm just a lowely extension developer, but I have managed to get a couple of patches checked in. Just because you don't have CVS commit access doesn't mean they won't except your patch. Its all about chasing down bugs and then finding someone to review, super-review your work.
Those plans have morphed somewhat, but are in fact still a live. They are now called libxul or xulrunner, and I believe are part of the Mozilla 2.0 plan.
There is currently a ton of work being done on Sunbird. The backend is being rewritten to allow multiple calendar type providers, and the frontend is being cleaned up to match the new backend. Check out the calendar portion of: Mozilla Wiki for more details.
That's Bug # 236755