Skip to content

Commit

Permalink
fix: correct Firefox bug link texts
Browse files Browse the repository at this point in the history
In mdn#24834, some Firefox bug links were
accidentally labeled as "Webkit bug".
  • Loading branch information
caugner committed Nov 2, 2023
1 parent 858b1eb commit cc63ee3
Show file tree
Hide file tree
Showing 38 changed files with 115 additions and 115 deletions.
2 changes: 1 addition & 1 deletion files/en-us/mozilla/firefox/releases/2/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<textbox>` 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 `<textbox>` 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

Expand Down
2 changes: 1 addition & 1 deletion files/en-us/mozilla/firefox/releases/20/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
8 changes: 4 additions & 4 deletions files/en-us/mozilla/firefox/releases/27/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/).
Expand Down Expand Up @@ -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)).

Expand All @@ -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

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ NS_QueryNotificationCallbacks(channel, loadContext);
## Customizable toolbars
In Firefox 3.5, customizable toolbar behavior has changed such that the `<xul:toolbar/>` binding now removes toolbar items from its associated `<xul:toolbarpalette/>` 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 `<xul:toolbarpalette/>`, 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 `<xul:toolbar/>` binding now removes toolbar items from its associated `<xul:toolbarpalette/>` 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 `<xul:toolbarpalette/>`, 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
Expand Down
10 changes: 5 additions & 5 deletions files/en-us/mozilla/firefox/releases/3/dom_improvements/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down
30 changes: 15 additions & 15 deletions files/en-us/mozilla/firefox/releases/3/notable_bugs_fixed/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<menupopup>` 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 `<?xml-stylesheet ?>`, 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, `<?xml-stylesheet ?>` and `<?xul-overlay ?>` 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 `<menupopup>` 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 `<?xml-stylesheet ?>`, 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, `<?xml-stylesheet ?>` and `<?xul-overlay ?>` 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

Expand Down
Loading

0 comments on commit cc63ee3

Please sign in to comment.