#Mozilla firefox refresh page install
#Mozilla firefox refresh page update
#Mozilla firefox refresh page download

#Mozilla firefox refresh page download

Improve download handling across multiple sessionsĬreate document-parsing framework for detecting microformatsĬreate API for developers to leverage the microformat detection framework Integrate download manager with third-party virus scanners and malware protection Minimize/remove local MIME type database for local applicationsĮasier retrieval of files that a user has downloaded in the past Support all media types on all platforms as best we canĬreate an easy-to-use MIME type handling configuration system

#Mozilla firefox refresh page install

It should be easy to locate and install missing plugins Should be able to play all popular media formats when plugins/codecs are installed Support web services as protocol handlersīug 380415 and dependents Feature Requirements which links directly to related Add-on categories in AMO Small 'Add-on' button on managers, dialogs, etc. Same as CON-002b - AMO and Plugin Finder Service Improve quality of results from Plugin Finders Providing a lower priv model for certain classes of extension Making signing a requirement or higher value in install experience Support for use of some kind of service for extension dependency resolution

#Mozilla firefox refresh page update

? This was add button for single extension update checkĪllow addons to control other types of extensions and ensuring that model is extensible Simplify task flow for updating single addons Requires backend changes to do this reasonably Install Add-on without requiring a browser restart Help documents should link to related Add-on categories on Promote the existence of Add-ons that could help the user accomplish their current task Support displaying information about the update in the updaterīug 297903 Would be more useful with bug 102699īug 382312 Proposed Implementation - needs review by submitter (shaver?) Simplify language and unify terminology related to Add-ons The button now appears in a notification only when needed. Improve discoverability of Add-on configuration UIĪdd visual indication to browser UI when Add-on updates are availableįx3 fix implemented in bug 394645, will re-evaluate whether this is enough for Fx4Īdd permanent button for restarting Firefoxīug 369075. Support shipping of localized user-facing addon textĪdd-ons can be installed in fewer mouse clicksĪMO is integrated into the Manager, but that was not part of the original req.Įnsure user understands the risks about installing extensionsĬlarify XPi install dialogs and user interactionsīug 252830 note: the (xpinstall) whitelist is for both plugins and extensionsĪllow Add-on configuration UI to be accessed from main application configuration UI Note that it's possible that Firefox may alert the user that your extension uses the contentaccessible flag in this way, as it does constitute a potential security risk.Unify add-ons management system and add plugin management systemīug 382367 for backend changes. This shouldn't be something you need to do very often, but it's available for those rare cases in which it's needed. They can specify a special flag in their chrome.manifest file, like this: content mypackage location/ contentaccessible=yes There is, however, a way for extensions to make their content web-accessible. All other chrome content is now blocked from access by the web. These files are intended to be accessible by web content. Among other things, this made it possible for sites to detect the presence of add-ons - which could be used to breach a user's security by bypassing add-ons that add security features to the browser.įirefox 3 only allows web content to access items in the chrome://browser/ and chrome://toolkit/ spaces. In prior versions of Firefox, any web page could load scripts or images from chrome using the chrome:// protocol. See bug 434718, especially its NOT A CASE FOR THE BUG TEMPLATE - The following link points to a Bugzilla attachment, not a Bugzilla bug if you use the attachment number as a bug number, it becomes nonsense attachment 322943 NOT A CASE FOR THE BUG TEMPLATE for a demonstration (must be watched with a minimum font size >= 6 to see the difference: the two box cascades behave differently in Firefox 2, because the em-based font-size 'bounces' off the minimum font size). In other words, font sizes are always calculated according to the designer's intention and are adjusted for minimum font size afterwards. This was inconsistent with the way percentage-based font sizes behaved.įont-size values in em and ex units are now based on an 'intended font size' that is not affected by the user's minimum font size. Font-size values in em and ex units used to be affected by the user's minimum font size setting: if a font was displayed larger due to the minimum font size, the em and ex units for font-size settings based on this one would be enlarged accordingly.