From cc63ee3d29acc81a7e39cfa249ea91a38b1e197e Mon Sep 17 00:00:00 2001 From: Claas Augner Date: Thu, 2 Nov 2023 21:56:00 +0100 Subject: [PATCH] fix: correct Firefox bug link texts In https://github.com/mdn/content/pull/24834, some Firefox bug links were accidentally labeled as "Webkit bug". --- .../en-us/mozilla/firefox/releases/2/index.md | 2 +- .../mozilla/firefox/releases/20/index.md | 2 +- .../mozilla/firefox/releases/27/index.md | 8 ++-- .../releases/3.5/updating_extensions/index.md | 2 +- .../releases/3/dom_improvements/index.md | 10 ++--- .../releases/3/notable_bugs_fixed/index.md | 30 +++++++-------- .../releases/3/site_compatibility/index.md | 8 ++-- .../releases/3/svg_improvements/index.md | 6 +-- .../firefox/releases/3/templates/index.md | 4 +- .../releases/3/updating_extensions/index.md | 12 +++--- .../3/updating_web_applications/index.md | 2 +- .../3/xul_improvements_in_firefox_3/index.md | 14 +++---- .../mozilla/firefox/releases/31/index.md | 38 +++++++++---------- .../mozilla/firefox/releases/32/index.md | 22 +++++------ .../en-us/mozilla/firefox/releases/4/index.md | 4 +- .../mozilla/firefox/releases/41/index.md | 2 +- .../en-us/mozilla/firefox/releases/6/index.md | 4 +- .../releases/6/updating_add-ons/index.md | 2 +- .../mozilla/firefox/releases/66/index.md | 6 +-- .../mozilla/firefox/releases/70/index.md | 16 ++++---- .../document/getelementsbytagname/index.md | 2 +- .../comparison_of_event_targets/index.md | 2 +- .../api/event/explicitoriginaltarget/index.md | 2 +- .../idbdatabase/createobjectstore/index.md | 2 +- .../web/api/idbdatabase/transaction/index.md | 2 +- .../api/idbobjectstore/createindex/index.md | 2 +- files/en-us/web/api/idbtransaction/index.md | 2 +- .../indexeddb_api/basic_terminology/index.md | 2 +- .../indexeddb_api/using_indexeddb/index.md | 2 +- files/en-us/web/api/window/find/index.md | 2 +- .../en-us/web/api/window/ondragdrop/index.md | 2 +- .../api/workerglobalscope/location/index.md | 2 +- .../xmlhttprequest/xmlhttprequest/index.md | 2 +- .../css/-moz-force-broken-image-icon/index.md | 2 +- .../en-us/web/css/mozilla_extensions/index.md | 2 +- .../index.md | 2 +- .../http/headers/user-agent/firefox/index.md | 2 +- files/en-us/web/opensearch/index.md | 2 +- 38 files changed, 115 insertions(+), 115 deletions(-) diff --git a/files/en-us/mozilla/firefox/releases/2/index.md b/files/en-us/mozilla/firefox/releases/2/index.md index 19e9475619a705d..7f257f4cff2b1d2 100644 --- a/files/en-us/mozilla/firefox/releases/2/index.md +++ b/files/en-us/mozilla/firefox/releases/2/index.md @@ -58,7 +58,7 @@ Firefox 2 introduces a vast array of new features and capabilities. This article - [Theme changes in Firefox 2](/en-US/docs/Theme_changes_in_Firefox_2) - : Discusses the changes needed to update existing themes to work in Firefox 2. - Textbox Improvements (Firefox 2.0.0.1 and higher only) - - : The `` now has a `reset()` method to reset the value of the textbox to the default value. The `defaultValue` property may be used to retrieve and modify the default value of the textbox ([Webkit bug 312867](https://bugzil.la/312867)). Supports an `editor` property to get the internal `nsIEditor` for the text field ([Webkit bug 312867](https://bugzil.la/312867)). + - : The `` now has a `reset()` method to reset the value of the textbox to the default value. The `defaultValue` property may be used to retrieve and modify the default value of the textbox ([Firefox bug 312867](https://bugzil.la/312867)). Supports an `editor` property to get the internal `nsIEditor` for the text field ([Webkit bug 312867](https://bugzil.la/312867)). ## New features for end users diff --git a/files/en-us/mozilla/firefox/releases/20/index.md b/files/en-us/mozilla/firefox/releases/20/index.md index fe58cf008e55616..f5459da7fbda3d9 100644 --- a/files/en-us/mozilla/firefox/releases/20/index.md +++ b/files/en-us/mozilla/firefox/releases/20/index.md @@ -21,7 +21,7 @@ Firefox 20 was released on April, 2nd 2013. This article provides information ab - Support for the `WeakMap.prototype.clear()` method, recently added to the Harmony (ECMAScript 2015) draft proposal has been added ([Firefox bug 814562](https://bugzil.la/814562)). - Support for the [`Math.imul()`](/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/imul) method, a C-style 32-bit multiplication function. Though proposed for Harmony (ECMAScript 2015) it has not yet accepted and still is non-standard ([Firefox bug 808148](https://bugzil.la/808148)). - Web apps using draggable text with Kinetic 3.x are working, even when using the Cairo canvas backend ([Firefox bug 835064](https://bugzil.la/835064)). -- The [`for each...in`](/en-US/docs/JavaScript/Reference/Statements/for_each...in) statement has been deprecated and should not be used. Consider using the new [`for...of`](/en-US/docs/Web/JavaScript/Reference/Statements/for...of) statement ([Webkit bug 804834](https://bugzil.la/804834)). +- The [`for each...in`](/en-US/docs/JavaScript/Reference/Statements/for_each...in) statement has been deprecated and should not be used. Consider using the new [`for...of`](/en-US/docs/Web/JavaScript/Reference/Statements/for...of) statement ([Firefox bug 804834](https://bugzil.la/804834)). - Support for the {{jsxref("Map.prototype.keys()")}}, {{jsxref("Map.prototype.values()")}}, and {{jsxref("Map.prototype.entries()")}} has been added ([Firefox bug 817368](https://bugzil.la/817368)). ### CSS diff --git a/files/en-us/mozilla/firefox/releases/27/index.md b/files/en-us/mozilla/firefox/releases/27/index.md index 971505911e2e8d5..52e7bee5e57acf7 100644 --- a/files/en-us/mozilla/firefox/releases/27/index.md +++ b/files/en-us/mozilla/firefox/releases/27/index.md @@ -17,8 +17,8 @@ Firefox 27 was released on February 4, 2014. This article lists key changes that - The inspector now has an "edit-element-html" feature, without needing an add-on. - Background-URLs and colors have preview in inspector. Even hovering over canvas elements will give a pop-up with an image preview. - Reflow logging has been added. -- Styles of SVG elements are now inspectable ([Webkit bug 921191](https://bugzil.la/921191)). -- Failure to find the image when clicking URL link in CSS inspector has been fixed ([Webkit bug 921686](https://bugzil.la/921686)). +- Styles of SVG elements are now inspectable ([Firefox bug 921191](https://bugzil.la/921191)). +- Failure to find the image when clicking URL link in CSS inspector has been fixed ([Firefox bug 921686](https://bugzil.la/921686)). - The {{HTTPHeader("SourceMap", "X-SourceMap")}} header is now supported ([Firefox bug 765993](https://bugzil.la/765993)). More details in [this post](https://hacks.mozilla.org/2013/11/firefox-developer-tools-episode-27-edit-as-html-codemirror-more/). @@ -64,7 +64,7 @@ More details in [this post](https://hacks.mozilla.org/2013/11/firefox-developer- - `Event.isTrusted()` is now unforgeable ([Firefox bug 637248](https://bugzil.la/637248)). - The WebRTC API's {{domxref("RTCIceCandidate")}} object now includes a {{domxref("RTCIceCandidate.toJSON", "toJSON()")}} method to help with signaling and debugging ([Firefox bug 928304](https://bugzil.la/928304)). - The {{domxref("Navigator.vibrate()")}} method has been adapted to match the final specification: It now returns `false` when the list is too long or has too large entries, instead of throwing ([Firefox bug 884935](https://bugzil.la/884935)). -- As part of the ongoing effort to standardize global objects, the non-standard stylesheet change event interfaces, including `StyleRuleChangeEvent`, `StyleSheetApplicableStateChangeEvent` and `StyleSheetChangeEvent`, are no longer available from Web content. The `CSSGroupRuleRuleList` interface, the implementation detail of {{domxref("CSSRuleList")}}, has also been removed ([Webkit bug 872934](https://bugzil.la/872934) and [Firefox bug 916871](https://bugzil.la/916871)). +- As part of the ongoing effort to standardize global objects, the non-standard stylesheet change event interfaces, including `StyleRuleChangeEvent`, `StyleSheetApplicableStateChangeEvent` and `StyleSheetChangeEvent`, are no longer available from Web content. The `CSSGroupRuleRuleList` interface, the implementation detail of {{domxref("CSSRuleList")}}, has also been removed ([Firefox bug 872934](https://bugzil.la/872934) and [Firefox bug 916871](https://bugzil.la/916871)). - `atob` now ignores whitespaces ([Firefox bug 711180](https://bugzil.la/711180)). - [WebGL](/en-US/docs/Web/API/WebGL_API): `MOZ_` prefixed extension strings are deprecated. Support for them will be removed in the future. Use unprefixed extension string only. To get draft extensions, set the `webgl.enable-draft-extensions` preferences ([Firefox bug 924176](https://bugzil.la/924176)). @@ -83,7 +83,7 @@ _No change._ ## Security -- TLS 1.2 has been implemented for improved security ([Webkit bug 861266](https://bugzil.la/861266)). +- TLS 1.2 has been implemented for improved security ([Firefox bug 861266](https://bugzil.la/861266)). ## See also diff --git a/files/en-us/mozilla/firefox/releases/3.5/updating_extensions/index.md b/files/en-us/mozilla/firefox/releases/3.5/updating_extensions/index.md index be422216ebbc307..ff1a43ee6d7aa73 100644 --- a/files/en-us/mozilla/firefox/releases/3.5/updating_extensions/index.md +++ b/files/en-us/mozilla/firefox/releases/3.5/updating_extensions/index.md @@ -180,7 +180,7 @@ NS_QueryNotificationCallbacks(channel, loadContext); ## Customizable toolbars -In Firefox 3.5, customizable toolbar behavior has changed such that the `` binding now removes toolbar items from its associated `` and adds them to the toolbar, rather than cloning them and copying them to the toolbar. This means that the palette will now only contain items not present on the toolbar, as opposed to the previous behavior of containing all customizable elements whether or not they were displayed on the toolbar. This might cause trouble for addons that depend on being able to retrieve all customizable toolbar items from the ``, or which attempt to dynamically insert items into the palette to make them available during toolbar customization. More information is available in [Webkit bug 407725](https://bugzil.la/407725) and [Webkit bug 467045](https://bugzil.la/467045). +In Firefox 3.5, customizable toolbar behavior has changed such that the `` binding now removes toolbar items from its associated `` and adds them to the toolbar, rather than cloning them and copying them to the toolbar. This means that the palette will now only contain items not present on the toolbar, as opposed to the previous behavior of containing all customizable elements whether or not they were displayed on the toolbar. This might cause trouble for addons that depend on being able to retrieve all customizable toolbar items from the ``, or which attempt to dynamically insert items into the palette to make them available during toolbar customization. More information is available in [Firefox bug 407725](https://bugzil.la/407725) and [Webkit bug 467045](https://bugzil.la/467045). ## XPCNativeWrapper diff --git a/files/en-us/mozilla/firefox/releases/3/dom_improvements/index.md b/files/en-us/mozilla/firefox/releases/3/dom_improvements/index.md index e559dd1227d36ee..a2e62b1b234c42f 100644 --- a/files/en-us/mozilla/firefox/releases/3/dom_improvements/index.md +++ b/files/en-us/mozilla/firefox/releases/3/dom_improvements/index.md @@ -9,11 +9,11 @@ page-type: guide Firefox 3 offers a number of improvements to the [Document Object Model](/en-US/docs/Web/API/Document_Object_Model) (DOM), especially in regard to support for extensions to the DOM added by other browsers. This article provides a list of those improvements as well as links to more detailed documentation. - The Internet Explorer [`clientTop`](/en-US/docs/Web/API/Element/clientTop) and [`clientLeft`](/en-US/docs/Web/API/Element/clientLeft) DOM extensions are now supported. -- The [`window.fullScreen`](/en-US/docs/Web/API/Window/fullScreen) property is now always accurate no matter where it is read, even in content. Previously it would return `false` inaccurately ([Webkit bug 127013](https://bugzil.la/127013)). -- The [`getClientRects`](/en-US/docs/Web/API/Element/getClientRects) and [`getBoundingClientRect`](/en-US/docs/Web/API/Element/getBoundingClientRect) DOM extensions are now supported (see [Webkit bug 174397](https://bugzil.la/174397)). -- The Internet Explorer [`elementFromPoint`](/en-US/docs/Web/API/Document/elementFromPoint) DOM extension is now supported ([Webkit bug 199692](https://bugzil.la/199692)). -- The Internet Explorer [`oncut`](/en-US/docs/Web/API/HTMLElement/cut_event), [`oncopy`](/en-US/docs/Web/API/HTMLElement/copy_event), and [`onpaste`](/en-US/docs/Web/API/HTMLElement/paste_event) DOM extensions are now supported ([Webkit bug 280959](https://bugzil.la/280959)). -- Added privileged-code-only getters for `Node.nodePrincipal`, `Node.baseURIObject`, and `document.documentURIObject`. Chrome code must not touch (get or set) these properties on an unwrapped content object (e.g. on a `wrappedJSObject` of an [`XPCNativeWrapper`](/en-US/XPCNativeWrapper)), see [Webkit bug 324464](https://bugzil.la/324464) for details. +- The [`window.fullScreen`](/en-US/docs/Web/API/Window/fullScreen) property is now always accurate no matter where it is read, even in content. Previously it would return `false` inaccurately ([Firefox bug 127013](https://bugzil.la/127013)). +- The [`getClientRects`](/en-US/docs/Web/API/Element/getClientRects) and [`getBoundingClientRect`](/en-US/docs/Web/API/Element/getBoundingClientRect) DOM extensions are now supported (see [Firefox bug 174397](https://bugzil.la/174397)). +- The Internet Explorer [`elementFromPoint`](/en-US/docs/Web/API/Document/elementFromPoint) DOM extension is now supported ([Firefox bug 199692](https://bugzil.la/199692)). +- The Internet Explorer [`oncut`](/en-US/docs/Web/API/HTMLElement/cut_event), [`oncopy`](/en-US/docs/Web/API/HTMLElement/copy_event), and [`onpaste`](/en-US/docs/Web/API/HTMLElement/paste_event) DOM extensions are now supported ([Firefox bug 280959](https://bugzil.la/280959)). +- Added privileged-code-only getters for `Node.nodePrincipal`, `Node.baseURIObject`, and `document.documentURIObject`. Chrome code must not touch (get or set) these properties on an unwrapped content object (e.g. on a `wrappedJSObject` of an [`XPCNativeWrapper`](/en-US/XPCNativeWrapper)), see [Firefox bug 324464](https://bugzil.la/324464) for details. - The Web Applications 1.0 (HTML5) [`getElementsByClassName()`](/en-US/docs/Web/API/Document/getElementsByClassName) DOM method is now supported. - The Web Applications 1.0 (HTML5) [`window.postMessage`](/en-US/docs/Web/API/Window/postMessage) DOM method is now supported. This method allows a limited, opt-in form of client-side communication between windows not necessarily on the same domain. - The `charCode` value of the `keypress` event is changed to an ASCII character if the accelerator key is pressed. Otherwise the `charCode` is the unmodified character (excepting `Shift` state). See [Gecko Keypress Event](/en-US/Gecko_Keypress_Event). diff --git a/files/en-us/mozilla/firefox/releases/3/notable_bugs_fixed/index.md b/files/en-us/mozilla/firefox/releases/3/notable_bugs_fixed/index.md index 5fb8720031a852e..12deca6efa57b85 100644 --- a/files/en-us/mozilla/firefox/releases/3/notable_bugs_fixed/index.md +++ b/files/en-us/mozilla/firefox/releases/3/notable_bugs_fixed/index.md @@ -8,21 +8,21 @@ page-type: guide This article offers a list of important bug fixes offered by Firefox 3 that are not necessarily obvious in the documentation. -- if an error occurs parsing an overlay, the overlay is not applied. Parse errors are logged to the error console. ([Webkit bug 335755](https://bugzil.la/335755)) -- bug fixed where `` elements can be placed inside a binding when attached to a menu or menu-like element. ([Webkit bug 345896](https://bugzil.la/345896)) -- the button's `dlgType` property now works properly. ([Webkit bug 308591](https://bugzil.la/308591)) -- the `canBubble` argument to {{ Domxref("event.initEvent") }} now works properly so that events can be fired which don't bubble. ([Webkit bug 330190](https://bugzil.la/330190)) -- the `DOMAttrModified` event now handles namespaced attributes properly. ([Webkit bug 362391](https://bugzil.la/362391)) -- XML processing instructions, such as ``, are now added to a XUL document's DOM. This means {{ Domxref("Node.firstChild", "document.firstChild") }} isn't guaranteed to be the root element, use {{ Domxref("document.documentElement") }} instead. Also, `` and `` processing instructions now have no effect outside the document prolog. ([Webkit bug 319654](https://bugzil.la/319654)) -- [`getElementsByAttributeNS()`](/en-US/docs/Mozilla/Tech/XUL/Method/getElementsByAttributeNS) functions have been added to XUL elements and documents. ([Webkit bug 239976](https://bugzil.la/239976)) -- event listeners are maintained when moving or removing an element from a XUL document. ([Webkit bug 286619](https://bugzil.la/286619)) -- mutation events are now fired for non-displayed documents. ([Webkit bug 201236](https://bugzil.la/201236)) -- various issues with elements drawing in the wrong order are fixed. ([Webkit bug 317375](https://bugzil.la/317375)) -- [`getElementsByTagName()`](/en-US/docs/Web/API/Element/getElementsByTagName) has been fixed to work correctly on subtrees that have elements with namespace prefixes in their tag names ([Webkit bug 206053](https://bugzil.la/206053)). -- The `DOMNodeInserted` and `DOMNodeRemoved` events now properly apply to the correct nodes ([Webkit bug 367164](https://bugzil.la/367164)). -- `\d`, one of special characters in regular expressions, has been fixed to match only Basic Latin alphabet digits (equivalent to `[0-9]`). ([Webkit bug 378738](https://bugzil.la/378738)) -- The image-sniffing-services category allows for image decoders implemented as extensions to correctly decode images sent with incorrect mime-types. ([Webkit bug 391667](https://bugzil.la/391667)) -- Right-clicks on form controls no longer brings up a context menu by default ([Webkit bug 404536](https://bugzil.la/404536). See [Offering a context menu for form controls](/en-US/docs/Offering%20a%20context%20menu%20for%20form%20controls) to learn how to enable this on a case-by-case basis. +- if an error occurs parsing an overlay, the overlay is not applied. Parse errors are logged to the error console. ([Firefox bug 335755](https://bugzil.la/335755)) +- bug fixed where `` elements can be placed inside a binding when attached to a menu or menu-like element. ([Firefox bug 345896](https://bugzil.la/345896)) +- the button's `dlgType` property now works properly. ([Firefox bug 308591](https://bugzil.la/308591)) +- the `canBubble` argument to {{ Domxref("event.initEvent") }} now works properly so that events can be fired which don't bubble. ([Firefox bug 330190](https://bugzil.la/330190)) +- the `DOMAttrModified` event now handles namespaced attributes properly. ([Firefox bug 362391](https://bugzil.la/362391)) +- XML processing instructions, such as ``, are now added to a XUL document's DOM. This means {{ Domxref("Node.firstChild", "document.firstChild") }} isn't guaranteed to be the root element, use {{ Domxref("document.documentElement") }} instead. Also, `` and `` processing instructions now have no effect outside the document prolog. ([Firefox bug 319654](https://bugzil.la/319654)) +- [`getElementsByAttributeNS()`](/en-US/docs/Mozilla/Tech/XUL/Method/getElementsByAttributeNS) functions have been added to XUL elements and documents. ([Firefox bug 239976](https://bugzil.la/239976)) +- event listeners are maintained when moving or removing an element from a XUL document. ([Firefox bug 286619](https://bugzil.la/286619)) +- mutation events are now fired for non-displayed documents. ([Firefox bug 201236](https://bugzil.la/201236)) +- various issues with elements drawing in the wrong order are fixed. ([Firefox bug 317375](https://bugzil.la/317375)) +- [`getElementsByTagName()`](/en-US/docs/Web/API/Element/getElementsByTagName) has been fixed to work correctly on subtrees that have elements with namespace prefixes in their tag names ([Firefox bug 206053](https://bugzil.la/206053)). +- The `DOMNodeInserted` and `DOMNodeRemoved` events now properly apply to the correct nodes ([Firefox bug 367164](https://bugzil.la/367164)). +- `\d`, one of special characters in regular expressions, has been fixed to match only Basic Latin alphabet digits (equivalent to `[0-9]`). ([Firefox bug 378738](https://bugzil.la/378738)) +- The image-sniffing-services category allows for image decoders implemented as extensions to correctly decode images sent with incorrect mime-types. ([Firefox bug 391667](https://bugzil.la/391667)) +- Right-clicks on form controls no longer brings up a context menu by default ([Firefox bug 404536](https://bugzil.la/404536). See [Offering a context menu for form controls](/en-US/docs/Offering%20a%20context%20menu%20for%20form%20controls) to learn how to enable this on a case-by-case basis. ### See also diff --git a/files/en-us/mozilla/firefox/releases/3/site_compatibility/index.md b/files/en-us/mozilla/firefox/releases/3/site_compatibility/index.md index 7275167ffbd5141..62028d1ced182c1 100644 --- a/files/en-us/mozilla/firefox/releases/3/site_compatibility/index.md +++ b/files/en-us/mozilla/firefox/releases/3/site_compatibility/index.md @@ -14,7 +14,7 @@ See also [Firefox 3 for developers](/en-US/Firefox_3_for_developers). ### Capturing load event listeners -In Gecko 1.8, it was not possible to set capturing load event listeners on images. In Gecko 1.9, this has been fixed by [Webkit bug 234455](https://bugzil.la/234455). But this can cause problems on websites that incorrectly have their event listeners set to capture the load event. See the discussion in [Webkit bug 335251](https://bugzil.la/335251). To fix this problem, the problematic page in question should not set a capturing load event listener. +In Gecko 1.8, it was not possible to set capturing load event listeners on images. In Gecko 1.9, this has been fixed by [Firefox bug 234455](https://bugzil.la/234455). But this can cause problems on websites that incorrectly have their event listeners set to capture the load event. See the discussion in [Webkit bug 335251](https://bugzil.la/335251). To fix this problem, the problematic page in question should not set a capturing load event listener. For example, this: @@ -32,7 +32,7 @@ For an explanation of how event capture works, see [DOM Level 2 Event capture](h ### `preventBubble` has been removed -In Gecko 1.8, the `preventBubble` method existed on events to prevent events from bubbling upwards. In Gecko 1.9 this method has been removed. Instead, you should use the standard [stopPropagation()](/en-US/docs/Web/API/Event/stopPropagation), which also works fine in Gecko 1.8. The patch in [Webkit bug 330494](https://bugzil.la/330494) made this happen. See also [Webkit bug 105280](https://bugzil.la/105280). +In Gecko 1.8, the `preventBubble` method existed on events to prevent events from bubbling upwards. In Gecko 1.9 this method has been removed. Instead, you should use the standard [stopPropagation()](/en-US/docs/Web/API/Event/stopPropagation), which also works fine in Gecko 1.8. The patch in [Firefox bug 330494](https://bugzil.la/330494) made this happen. See also [Webkit bug 105280](https://bugzil.la/105280). ### A few other old event APIs are no longer supported @@ -50,13 +50,13 @@ Firefox doesn't currently enforce this rule (it did for a while during the devel ### `intersectsNode` has been removed -In Gecko 1.8 the function `intersectsNode` code be used to test if a node intersected a range. However the return values from this function were confusing and rarely useful and has therefore been removed in Gecko 1.9. Instead use the more precise and standard function [compareBoundaryPoints](/en-US/docs/Web/API/Range/compareBoundaryPoints). The patch in [Webkit bug 358073](https://bugzil.la/358073) removed this function. +In Gecko 1.8 the function `intersectsNode` code be used to test if a node intersected a range. However the return values from this function were confusing and rarely useful and has therefore been removed in Gecko 1.9. Instead use the more precise and standard function [compareBoundaryPoints](/en-US/docs/Web/API/Range/compareBoundaryPoints). The patch in [Firefox bug 358073](https://bugzil.la/358073) removed this function. See the documentation for [intersectsNode](/en-US/docs/Web/API/Range/intersectsNode) for how to use `compareBoundaryPoints` instead. ### `compareNode` has been removed -In Gecko 1.8 the function `compareNode` code be used to test how a node intersected a range. However the return values from this function were confusing and rarely useful and has therefore been removed in Gecko 1.9. Instead use the more precise and standard function [compareBoundaryPoints](/en-US/docs/Web/API/Range/compareBoundaryPoints). The patch in [Webkit bug 358073](https://bugzil.la/358073) removed this function. +In Gecko 1.8 the function `compareNode` code be used to test how a node intersected a range. However the return values from this function were confusing and rarely useful and has therefore been removed in Gecko 1.9. Instead use the more precise and standard function [compareBoundaryPoints](/en-US/docs/Web/API/Range/compareBoundaryPoints). The patch in [Firefox bug 358073](https://bugzil.la/358073) removed this function. See the documentation for [compareNode](/en-US/docs/Web/API/Range/compareNode) for how to use `compareBoundaryPoints` instead. diff --git a/files/en-us/mozilla/firefox/releases/3/svg_improvements/index.md b/files/en-us/mozilla/firefox/releases/3/svg_improvements/index.md index 9d458d5a5a3c5cb..5c975d5f3e63e97 100644 --- a/files/en-us/mozilla/firefox/releases/3/svg_improvements/index.md +++ b/files/en-us/mozilla/firefox/releases/3/svg_improvements/index.md @@ -8,7 +8,7 @@ page-type: guide Firefox 3 offers improved [Scalable Vector Graphics](/en-US/docs/Web/SVG) (SVG) support over prior versions of Firefox. While these features are documented elsewhere, this article serves as a convenient list so you can easily determine which features were added in Firefox 3. -- The `foreignObject` element is now supported ([Webkit bug 326966](https://bugzil.la/326966)). See the [specification](https://www.w3.org/TR/SVG11/extend.html#ForeignObjectElement) or [this article](https://robert.ocallahan.org/2006/06/future-is-now_20.html) for details. +- The `foreignObject` element is now supported ([Firefox bug 326966](https://bugzil.la/326966)). See the [specification](https://www.w3.org/TR/SVG11/extend.html#ForeignObjectElement) or [this article](https://robert.ocallahan.org/2006/06/future-is-now_20.html) for details. - `pattern` element support ([spec](https://www.w3.org/TR/SVG11/pservers.html#PatternElement)) - `mask` element support ([spec](https://www.w3.org/TR/SVG11/masking.html#MaskElement)) - Support for all SVG 1.1 filters ([spec](https://www.w3.org/TR/SVG11/filters.html)): @@ -37,11 +37,11 @@ Firefox 3 offers improved [Scalable Vector Graphics](/en-US/docs/Web/SVG) (SVG) - `feTurbulence` - `feTile` -- `` element handling in SVG has had several bugs fixed; see [Webkit bug 267664](https://bugzil.la/267664), [Webkit bug 268135](https://bugzil.la/268135), [Webkit bug 316248](https://bugzil.la/316248), [Webkit bug 317270](https://bugzil.la/317270) and [Webkit bug 320724](https://bugzil.la/320724). +- `` element handling in SVG has had several bugs fixed; see [Firefox bug 267664](https://bugzil.la/267664), [Webkit bug 268135](https://bugzil.la/268135), [Webkit bug 316248](https://bugzil.la/316248), [Webkit bug 317270](https://bugzil.la/317270) and [Webkit bug 320724](https://bugzil.la/320724). - The SVG DOM Methods `getNumberOfChars()`, `getComputedTextLength()`, `getSubStringLength()`, `getStartPositionOfChar()`, `getEndPositionOfChar()`, `getRotationOfChar()`, and `getCharNumAtPosition()` have been implemented. - the `xml:space` attribute support ([spec](https://www.w3.org/TR/SVG/text.html#WhiteSpace)) - fallback `fill`/`stroke` are now supported ([spec](https://www.w3.org/TR/SVG/painting.html#SpecifyingPaint)) -- `em` and `ex` units are now supported for indicating lengths ([Webkit bug 305859](https://bugzil.la/305859)). +- `em` and `ex` units are now supported for indicating lengths ([Firefox bug 305859](https://bugzil.la/305859)). ## See also diff --git a/files/en-us/mozilla/firefox/releases/3/templates/index.md b/files/en-us/mozilla/firefox/releases/3/templates/index.md index 3cc19091f42c2ae..213c0ae259ae2df 100644 --- a/files/en-us/mozilla/firefox/releases/3/templates/index.md +++ b/files/en-us/mozilla/firefox/releases/3/templates/index.md @@ -6,14 +6,14 @@ page-type: guide {{FirefoxSidebar}} -Templates have been significantly improved in Firefox 3. The key improvement allows the use of [custom query processors](/en-US/docs/How_to_implement_a_custom_XUL_query_processor_component) to handle other types of datasources besides RDF. A new query syntax makes this possible. Built-in support for SQL ([mozStorage](/en-US/docs/Storage)) and XML datasources is also provided. A full description of the new features available for templates [is available](https://wiki.mozilla.org/XUL:Template_Features_in_1.9). ([Webkit bug 285631](https://bugzil.la/285631)) +Templates have been significantly improved in Firefox 3. The key improvement allows the use of [custom query processors](/en-US/docs/How_to_implement_a_custom_XUL_query_processor_component) to handle other types of datasources besides RDF. A new query syntax makes this possible. Built-in support for SQL ([mozStorage](/en-US/docs/Storage)) and XML datasources is also provided. A full description of the new features available for templates [is available](https://wiki.mozilla.org/XUL:Template_Features_in_1.9). ([Firefox bug 285631](https://bugzil.la/285631)) ### Other template improvements - Relational conditions have been added to allow for more precise control over what results match a rule. This allows, for example, matching of results that start or end with certain strings, or that are before or after other values. - A flag, `dont-recurse`, has been added to prevent recursion from happening such that only one level of results are generated - APIs have been added to the template builder to retrieve a result object representing an output item. -- The XUL sort service is more robust and [sorts](/en-US/docs/XUL/Template_Guide/Sorting_Results) both content and non-content trees better. It also allows sorting of non-template built content. ([Webkit bug 335122](https://bugzil.la/335122)) +- The XUL sort service is more robust and [sorts](/en-US/docs/XUL/Template_Guide/Sorting_Results) both content and non-content trees better. It also allows sorting of non-template built content. ([Firefox bug 335122](https://bugzil.la/335122)) ### See also diff --git a/files/en-us/mozilla/firefox/releases/3/updating_extensions/index.md b/files/en-us/mozilla/firefox/releases/3/updating_extensions/index.md index a3e8ada81df571e..56a968c356ebb8d 100644 --- a/files/en-us/mozilla/firefox/releases/3/updating_extensions/index.md +++ b/files/en-us/mozilla/firefox/releases/3/updating_extensions/index.md @@ -105,7 +105,7 @@ The following interfaces were removed from Gecko 1.9, which drives Firefox 3. If - `nsIDOMScrollListener` - `nsIDOMMutationListener` - `nsIDOMPageTransitionListener` -- `nsICloseAllWindows` (see [Webkit bug 386200](https://bugzil.la/386200)) +- `nsICloseAllWindows` (see [Firefox bug 386200](https://bugzil.la/386200)) ## Step 4: Check for relevant chrome changes @@ -150,16 +150,16 @@ Extensions that attempt to overlay onto the "appcontent" box try to float chrome _Add simple changes you had to make while updating your extension to work with Firefox 3 here._ - `chrome://browser/base/utilityOverlay.js` is no longer supported for security reasons. If you were previously using this, you should switch to `chrome://browser/content/utilityOverlay.js`. -- `nsIAboutModule` implementations are now required to support the `getURIFlags` method. See [nsIAboutModule.idl](https://dxr.mozilla.org/mozilla-central/source/netwerk/protocol/about/nsIAboutModule.idl) for documentation. This affects extensions that provide new `about:` URIs. ([Webkit bug 337746](https://bugzil.la/337746)) -- The [``](/en-US/docs/Mozilla/Tech/XUL/tabbrowser) element is no longer part of "toolkit" ([Webkit bug 339964](https://bugzil.la/339964)). This means this element is no longer available to XUL applications and extensions. It continues to be used in the main Firefox window (browser.xul). +- `nsIAboutModule` implementations are now required to support the `getURIFlags` method. See [nsIAboutModule.idl](https://dxr.mozilla.org/mozilla-central/source/netwerk/protocol/about/nsIAboutModule.idl) for documentation. This affects extensions that provide new `about:` URIs. ([Firefox bug 337746](https://bugzil.la/337746)) +- The [``](/en-US/docs/Mozilla/Tech/XUL/tabbrowser) element is no longer part of "toolkit" ([Firefox bug 339964](https://bugzil.la/339964)). This means this element is no longer available to XUL applications and extensions. It continues to be used in the main Firefox window (browser.xul). - Changes to `nsISupports_proxies` and possibly to threading-related interfaces need to be documented. -- If you use XML processing instructions, such as `` in your XUL files, be aware of the changes made in [Webkit bug 319654](https://bugzil.la/319654): +- If you use XML processing instructions, such as `` in your XUL files, be aware of the changes made in [Firefox bug 319654](https://bugzil.la/319654): 1. XML PIs are now added to a XUL document's DOM. This means {{ Domxref("Node.firstChild", "document.firstChild") }} is no longer guaranteed to be the root element. If you need to get the root document in your script, use {{ Domxref("document.documentElement") }} instead. 2. `` and `` processing instructions now have no effect outside the document prolog. -- `window.addEventListener("load", myFunc, true)` is not fired when loading web content (browser page loads). This is due to [Webkit bug 296639](https://bugzil.la/296639) which changes the way inner and outer windows communicate. The simple fix here is to use `gBrowser.addEventListener("load", myFunc, true)` as described [here](/en-US/docs/Code_snippets/Tabbed_browser#detecting_page_load) and works in Firefox 2 as well. +- `window.addEventListener("load", myFunc, true)` is not fired when loading web content (browser page loads). This is due to [Firefox bug 296639](https://bugzil.la/296639) which changes the way inner and outer windows communicate. The simple fix here is to use `gBrowser.addEventListener("load", myFunc, true)` as described [here](/en-US/docs/Code_snippets/Tabbed_browser#detecting_page_load) and works in Firefox 2 as well. - `content.window.getSelection()` gives an object (which can be converted to a string by `toString()`), unlike the now deprecated `content.document.getSelection()` which returns a string - `event.preventBubble()` was deprecated in Firefox 2 and has been removed in Firefox 3. Use [`event.stopPropagation()`](/en-US/docs/Web/API/Event/stopPropagation), which works in Firefox 2 as well. -- Timers that are initiated using `setTimeout()` are now blocked by modal windows due to the fix made for [Webkit bug 52209](https://bugzil.la/52209). You may use `nsITimer` instead. +- Timers that are initiated using `setTimeout()` are now blocked by modal windows due to the fix made for [Firefox bug 52209](https://bugzil.la/52209). You may use `nsITimer` instead. - If your extension needs to allow an untrusted source (e.g., a website) to access the extension's chrome, then you must use the new [`contentaccessible` flag](/en-US/docs/Chrome_Registration#contentaccessible). diff --git a/files/en-us/mozilla/firefox/releases/3/updating_web_applications/index.md b/files/en-us/mozilla/firefox/releases/3/updating_web_applications/index.md index 8fb1364ebe890e8..f1bf0298303e399 100644 --- a/files/en-us/mozilla/firefox/releases/3/updating_web_applications/index.md +++ b/files/en-us/mozilla/firefox/releases/3/updating_web_applications/index.md @@ -45,7 +45,7 @@ font-size values in em and ex units used to be affected by the user's minimum fo font-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. In other words, font sizes are always calculated according to the designer's intention and are adjusted for minimum font size afterwards. -See [Webkit bug 434718](https://bugzil.la/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](https://bug434718.bmoattachments.org/attachment.cgi?id=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). +See [Firefox bug 434718](https://bugzil.la/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](https://bug434718.bmoattachments.org/attachment.cgi?id=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). ## Security changes diff --git a/files/en-us/mozilla/firefox/releases/3/xul_improvements_in_firefox_3/index.md b/files/en-us/mozilla/firefox/releases/3/xul_improvements_in_firefox_3/index.md index ce572383067355e..486291a6a486642 100644 --- a/files/en-us/mozilla/firefox/releases/3/xul_improvements_in_firefox_3/index.md +++ b/files/en-us/mozilla/firefox/releases/3/xul_improvements_in_firefox_3/index.md @@ -13,18 +13,18 @@ Firefox 3 provides a number of new [XUL](/en-US/docs/XUL) elements, as well as i - [Numeric controls](/en-US/docs/XUL_Tutorial/Numeric_Controls): - The new [``](/en-US/docs/XUL/scale) element lets you create sliding scales that let the user select any value in a specified range. This widget would typically be used, for example, to create a volume control. - - A new value, `number`, for the `type` attribute of textboxes creates a textbox in which only numbers may be entered. In addition, arrow buttons appear to one side which may be used to step through values. [More information about numeric textboxes](https://wiki.mozilla.org/XUL:Specs:NumberBox). ([Webkit bug 345510](https://bugzil.la/345510)) - - A [``](/en-US/docs/XUL/spinbuttons) element is added which can be used when creating widgets using XBL bindings. ([Webkit bug 155053](https://bugzil.la/155053)) + - A new value, `number`, for the `type` attribute of textboxes creates a textbox in which only numbers may be entered. In addition, arrow buttons appear to one side which may be used to step through values. [More information about numeric textboxes](https://wiki.mozilla.org/XUL:Specs:NumberBox). ([Firefox bug 345510](https://bugzil.la/345510)) + - A [``](/en-US/docs/XUL/spinbuttons) element is added which can be used when creating widgets using XBL bindings. ([Firefox bug 155053](https://bugzil.la/155053)) - Two widgets, [``](/en-US/docs/XUL/datepicker) and [``](/en-US/docs/XUL/timepicker), can be used to allow the entry of dates and times. The datepicker is available in a number of styles by setting the `type` attribute, to allow entry with textboxes or a calendar grid. [More information about date pickers](https://wiki.mozilla.org/XUL:Specs:DateTimePickers) [Datepicker Reference](/en-US/docs/XUL/datepicker) [Timepicker Reference](/en-US/docs/XUL/timepicker) - A guide has been created for [menus and popups](/en-US/docs/XUL/PopupGuide) describing new features available: - - A [``](/en-US/docs/XUL/dropmarker) element is added which is useful when creating menu-like widgets using XBL bindings. ([Webkit bug 348614](https://bugzil.la/348614)) + - A [``](/en-US/docs/XUL/dropmarker) element is added which is useful when creating menu-like widgets using XBL bindings. ([Firefox bug 348614](https://bugzil.la/348614)) - The [``](/en-US/docs/XUL/panel) element is new and designed for popups that are not menus. They can support any type of content. The \ element should be used for menus. Menus provide keyboard navigation and support opening and closing submenus. ### Improvements to trees -- Trees can now be scrolled horizontally. If the columns don't fit into the available width, a horizontal scrollbar appears. This happens if the columns' specified widths add up to more than the available space. See [Webkit bug 212789](https://bugzil.la/212789) for details. +- Trees can now be scrolled horizontally. If the columns don't fit into the available width, a horizontal scrollbar appears. This happens if the columns' specified widths add up to more than the available space. See [Firefox bug 212789](https://bugzil.la/212789) for details. - A new selection style allows cells to be selected individually, instead of entire rows. To use this selection style, set the tree's `seltype` attribute to `cell`. - Trees now support editing of individual cells. When the user double-clicks an editable cell, a text field appears in which the user can edit the contents of the cell. See [these notes](https://wiki.mozilla.org/XUL:Tree) for details. - \ elements now support an `overflow` attribute which may be set to true to allow the text of cells within that column to expand to neighboring blank cells if the text is too large to fit into that single cell. @@ -37,9 +37,9 @@ Firefox 3 provides a number of new [XUL](/en-US/docs/XUL) elements, as well as i - The ``, `` and `` elements now have a readonly `selected` property which retrieves whether the item is selected in a \ - The ``, `` and `` elements now have a readonly `control` property which returns the enclosing \ - The ``, `` and `` elements now support the `accessKey`, `disabled`, `crop`, `image` and `label` properties which set the corresponding attribute -- The \ element now has methods to append, insert and remove menuitems. ([Webkit bug 372552](https://bugzil.la/372552)) +- The \ element now has methods to append, insert and remove menuitems. ([Firefox bug 372552](https://bugzil.la/372552)) - Editable menulists now offer an `editor` property to get the internal `nsIEditor` for its text field. -- Menus may now be made translucent on platforms that support it ([Webkit bug 70798](https://bugzil.la/70798)). +- Menus may now be made translucent on platforms that support it ([Firefox bug 70798](https://bugzil.la/70798)). ### Improvements to textboxes @@ -60,7 +60,7 @@ Firefox 3 provides a number of new [XUL](/en-US/docs/XUL) elements, as well as i - The `type` attribute on a `