Added the selection. Support for the window. Use personalbar instead. The window. This can be useful when testing performance of your web application.
The language token has been removed from window. Use window. Mouse events now include a mozPressure property indicating the amount of pressure on supported pressure-sensitive input devices. The DOMImplementation.
For example: element. See element. The document root now has a privatebrowsingmode attribute that describes the state of private browsing mode, including an indication of whether private browsing is temporary or permanent for the session. The second parameter of the window. The minimum allowed delay for the setTimeout method is now a preference, dom.
The MozAfterPaint event is no longer sent by default, due to a potential security issue. It can be re-enabled by setting a preference. User Agent string changes As a means to reduce the amount of data and entropy sent out in HTTP requests see bug , the crypto strength and language tokens have been removed from the user agent string.
Using the Web Console The Web Console tool is a useful debugging aid for web developers and extension developers alike. Add-ons Manager The new Add-ons Manager provides information about installed add-ons, support for managing them, and provides ways to install and remove add-ons.
Measuring performance using the PerfMeasurement. Miscellaneous changes to code modules The NetUtil. You can now use workers in JavaScript code modules. ChromeWorker A new type of worker for privileged code; this lets you use things like js-ctypes from workers in extensions and application code. Touch events Support for non-standard touch events has been added; these let you track multiple fingers moving on a touch screen at the same time.
Other DOM changes The new "document-element-inserted" notification is sent when a document's root element is created, but before any scripts are executed on it. Event listeners for those events should be added to gBrowser. It can therefore be overlaid directly with XUL overlays.
It can also be accessed more directly in JavaScript via gBrowser. See this blog post for more details. The new visibleTabs property was added to let you get an array of the currently visible tabs; this lets you determine which tabs are visible in the current tab set.
This is used by Firefox Panorama, for example. Added the new tabbrowser. The new pinTab and unpinTab methods let you pin and unpin tabs that is, switch them between being app tabs and regular tabs. If you continue using popup , you will encounter glitches, since the element has no special meaning anymore.
This also required the addition of a trigger event parameter to the openPopup method. Also, the anchorNode property has been added; it returns the anchor specified when the popup was created. The "active" attribute no longer gets set on active XUL windows. Instead, you can use the new :-moz-window-inactive pseudoclass in order to assign different styles to background windows. The emptytext attribute is now deprecated; you should use placeholder instead.
New TabPinned and TabUnpinned events are available, allowing you to detect when tabs are pinned and unpinned. The new TabAttrModified event is sent when a tab's label , crop , busy , image , or selected attributes change. This is used, for example, by the add-ons panel. Support has been added for logging XUL templates for debugging purposes. The add-on bar The status bar has been removed in favor of the new add-on bar.
Hiding browser chrome You can now hide the browser's chrome when it's desirable to do so; for example, about:addons does this. The mozIStorageStatement. Added the mozIStorageConnection. Places query results may now be observed by multiple observers, and queries may be executed asynchronously.
Some new notifications have been added to enable the browser to track the shutdown process of the Places service more reliably. Of these, most are for internal use only, but the places-connection-closed notification is available to know when the Places service has completed its shutdown process. The array size output parameter on several Places methods is now optional.
Instead, you need to create and populate a menu with Places information manually, instead of having it done for you. See Displaying Places information using views: Menu view for details. The nsIDocShell and nsIWebBrowser interfaces now have a new isActive attribute, which is used to allow optimization of code paths for documents that aren't currently visible. The nsIMemory method nsIMemory.
You should use "memory-pressure" notifications to watch for low memory situations instead. Any code that implements redirect handling using nsIChannelEventSink. This accepts a callback handler that must be called when a redirect is successfully completed.
The long-obsolete nsIPref interface has finally been removed. Your browser may have already done this for you. Double click the Firefox Disk Image to open it in Finder and drag the Firefox application onto your hard disk. Do not double click the icon in the disk image! Be sure to drag the Firefox application out of the disk image and onto your Hard Disk before running it.
If you have Nautilus set up to run Executable Text Files you can just double click firefox-installer to run. From the Start menu, choose Control Panel.
Find "Mozilla Firefox 1. These instructions leave your profile in place in case you install Firefox again in the future. If you wish to remove your profile folder, remove the location described below in the "Profile Folder" section. Note that by doing this you are destroying all of your Bookmarks, saved passwords, settings and other information and should you decide to use Firefox again you will be starting with a clean profile.
If you were using Firefox 0. You can remove the old "Phoenix" folder at your leisure. When you upgrade to a new version of Firefox all of your Extensions and Themes will be disabled until Firefox determines that either a they are compatible with the new release or b there are newer versions available that are compatible.
This is because Firefox changes from release to release and as such the ways in which some extensions integrate changes, meaning there can be problems when running an older extension with a newer version of Firefox. If you find that your favorite Extension or Theme has not been updated to be compatible with this release of Firefox, write the author and encourage them to update it.
This automatic updating of Extensions and Themes does not apply to users of Firefox 0. Those Extensions will be disabled when 1. To prevent the kind of problems we had with the 0. If you were using 0. This list covers some of the known problems with Firefox 1. Please read this before reporting any new bugs, and watch it regularly we'll update it as new bugs are found in the release. This system is for use by people who know what they are doing only, by changing a value incorrectly you may damage or destroy your Firefox installation!
Look to Help sites for handy preferences to tweak to customize Firefox further. If you uninstall an extension that is installed with your user profile i. If you do not do this you may end up with a jammed entry in the Extensions list and will be unable to install the extension globally.
If you encounter strange problems relating to bookmarks, downloads, window placement, toolbars, history, or other settings, it is recommended that you try creating a new profile and attempting to reproduce the problem before filing bugs. Create a new profile by running Firefox with the -P command line argument, choose the "Manage Profiles" button and then choose "Create Profile Migrate your settings files Bookmarks, Saved Passwords, etc over one by one, checking each time to see if the problems resurface.
If you do find a particular profile data file is causing a problem, file a bug and attach the file. We need all the exposure we can get. Make it your mission to convert as many of your friends, family members and coworkers as possible.
If you're a student, get it distributed at your college. Submit a story to Slashdot and other news sites about the release. Make some noise on your blog. Mass distribution via the Internet is possible -- look at Kazaa. Spread the word! If you're not using Firefox, tell the development team why.
We read the feedback at the Firefox forums. Use the forums. The Firefox team reads them regularly. We all get a lot of email and your email may get lost. Release Notes Get the details on the latest Firefox updates. Facebook Container Help prevent Facebook from collecting your data outside their site. Pocket Save and discover the best stories from across the web.
Mozilla VPN Get protection beyond your browser, on all your devices. Product Promise Learn how each Firefox product protects and respects your data. Firefox Relay Sign up for new accounts without handing over your email address. Mozilla Foundation Meet the not-for-profit behind Firefox that stands for a better web. Get involved Join the fight for a healthy internet. Careers Work for a mission-driven organization that makes people-first products. Mozilla Blog Learn about Mozilla and the issues that matter to us.
Close Innovation menu Mozilla Hubs Gather in this interactive, online, multi-dimensional social space.
0コメント