Intent to ship: Enable State Partitioning in Private Browsing Mode

# Summary We would like to enable State Partitioning[1] in private browsing windows. State Partitioning has been enabled in Strict Mode since Firefox 86[2] to provide better protection against trackers. Now, we want to expand the protection to the private browsing mode so that more users could ben

Intent to ship: Top Level Await

Top level await was prototyped in fall last year, and we are now confident with the implementation and the specification to move forward with shipping it. The proposal is in stage 3 of the TC39 Process[1]. There are no open issues which we are concerned about. Bug: https://bugzilla.mozilla.org/sho

Intent to ship: PerformanceEventTiming API

As of Firefox 89, I intend to turn PerformanceEventTiming API on by default on all channels. It has been developed behind the `dom.enable_event_timing` preference. Chrome has it enabled by default since 85. Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1701029 This fe

Intent to ship: Honoring bogo-XML declaration for character encoding in text/html

This has now landed and is expected to ride the trains in Firefox 89. For added historical context: Prior to HTML parsing getting specified, in addition to WebKit, also Gecko and Presto implemented this. At the time, the specification process paid too much attention to IE behavior as a presumed i

Re: intent to ship: sha2 windows signing

Per https://jira.mozilla.com/browse/RELENG-431, backwards compatibility with win7 sp0 may not be a big issue, though I'm happy to delay rollout if there are any additional concerns. I've linked sha2-signed artifacts in that ticket; we may want to have a QA pass before we decide to roll out. On Wed

intent to ship: sha2 windows signing

Per https://bugzilla.mozilla.org/show_bug.cgi?id=1697185#c4 and https://jira.mozilla.com/browse/RELENG-429 . We haven't made a product-level decision here, but a) it looks like timestamp.digicert.com may have silently EOLed sha1 timestamps since Microsoft has EOLed sha1 signing years ago, and b) i

Intent to ship: AbortSignal.abort()

I intend to implement and ship AbortSignal.abort() on all platforms. This is a shortcut function to create an aborted AbortSignal, similar to Promise.reject(). Standard: https://github.com/whatwg/dom/pull/960 WPT: https://github.com/web-platform-tests/wpt/pull/28003 Bugzilla: https://bugzilla.moz

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On 2021/03/10 21:23, Xidorn Quan wrote: On Wed, Mar 10, 2021, at 8:01 PM, Anne van Kesteren wrote: That does seem unfortunate, but unless other browsers are interested in picking this up, I think it will hurt us more to be different than that it helps. I don't think we should make aligning with

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On Wed, Mar 10, 2021, at 8:01 PM, Anne van Kesteren wrote: > That does seem unfortunate, but unless other browsers are interested > in picking this up, I think it will hurt us more to be different than > that it helps. I don't think we should make aligning with Chrome and > Safari conditional upon

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On Wed, Mar 10, 2021 at 9:11 AM Masayuki Nakano wrote: > Indeed, in long term goal must be that we'd dispatch exactly same wheel > events as Chrome/Chromium. However, without implementing alternative new > API, web apps will not be able to handle raw value for better UX. > Therefore, I filed a spe

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

Oops, On 2021/03/10 17:11, Masayuki Nakano wrote: Example 1: ``` addEventListener("wheel", event => {  let amount = event.deltaY;  if (isFirefox) {    amount *= 16;  }  scroll(amount);  event.preventDefault(); }); ``` Example 2: ``` addEventListener("wheel", event => {  let amount = even

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

Hi, Thank you Emilio for your great work! I'd like to explain the background. First, `WheelEvent` was designed for making it possible web browsers to expose raw wheel event information with 3 kinds of delta value modes which listeners can distinguish with `WheelEvent#deltaMode`. And then, I

Intent to Ship: AV1 Still Image File Format (AVIF)

As of March 18, 2021, I intend to turn AVIF on by default all platforms in Firefox 88. It has been developed behind the image.avif.enabled preference. Though there's a good chance it'll be delayed until Firefox 89, depending on some external factors. AVIF is an image format based on the AV1 video

Intent to ship: aspect-ratio property

p already last Oct. (Chromium intent to ship mail <https://groups.google.com/a/chromium.org/g/blink-dev/c/TF41VMfLhMI>) Safari: Implementing this feature, and has supported this in Safari Technology Preview. *Bug to turn on by default*: https://bugzilla.mozilla.org/show_bug.cgi?id=1672073 There a

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

Hello, So about experimenting with wheelEvent… Cool to see the work of Emilio in that space. Le 2021/03/10 à 07:13, Emilio Cobos Álvarez a écrit : > I guess we could enable the always-disabled pref on Nighly and watch for a > few releases to see if there's reports of broken sites. Would that s

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On 3/9/21 20:36, James Graham wrote: It seems like having all browsers have the same behaviour is going to be better in the long run than having some weird heuristic in gecko that acts as a footgun for authors going forward. Do we have any way to assess the compat impact of switching to match

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On 09/03/2021 18:21, Emilio Cobos Álvarez wrote: On 3/9/21 17:10, Anne van Kesteren wrote: On Tue, Mar 9, 2021 at 4:45 PM Emilio Cobos Álvarez wrote: Let me know if you have any concerns with this or what not. So if I understand it correctly we'll have a getter with side effects. Is the ex

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On 3/9/21 17:10, Anne van Kesteren wrote: On Tue, Mar 9, 2021 at 4:45 PM Emilio Cobos Álvarez wrote: Let me know if you have any concerns with this or what not. So if I understand it correctly we'll have a getter with side effects. Is the expectation that we can eventually remove this? Are o

Re: Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

On Tue, Mar 9, 2021 at 4:45 PM Emilio Cobos Álvarez wrote: > Let me know if you have any concerns with this or what not. So if I understand it correctly we'll have a getter with side effects. Is the expectation that we can eventually remove this? Are other browsers on board with this model? _

Intent to ship: Return pixel deltas in wheel event if deltaMode is not checked by authors

Hi, In bug 1696384, I plan to enable dom.event.wheel-deltaMode-lines.disabled on all channels. This is a compat intervention for sites that check WheelEvent.delta{X,Y,Z} before checking WheelEvent.deltaMode, generally assuming that the deltas are going to be pixels. These deltas are enviro

Intent to ship: WebAssembly SIMD

WebAssembly SIMD makes a large, common, and portable subset of the 128-bit vector instructions in many CPUs available to WebAssembly programs. SIMD helps speed up graphics, video/audio decoding/encoding, and machine learning workloads, to mention some. It is one of the most-requested features fro

Intent to ship: RegExp Match Indices

As of Firefox 88, we will support match indices in RegExps. Use case: Match Indices provide additional information about the start and end indices of captured substrings relative to the start of the input string. This information is only provided if the regexp has the /d flag set. For example:

Intent to ship: ETP strict mode shims for content-blocked resources (aka SmartBlock)

As of Firefox 87, I intend to enable ETP shims by default on desktop and Android. ETP shims are work-arounds for website breakage which is caused by blocking specific scripts in ETP strict mode and private browsing mode (see the intent to prototype for more context). Shims for the following scr

Intent to ship: make outlines follow border-radius automatically

The soft freeze is over, the change has been enabled for a few weeks on Nightly, and so far I've only seen progressions due to this change, so I think there's no reason to keep it Nightly-only. I've filed bug 1694146 to turn the pref on everywhere, so lacking objections or regressions due to t

Re: Intent to ship: beforeinput event and InputEvent.getTargetRanges()

On Fri, Jan 29, 2021 at 3:07 AM Masayuki Nakano wrote: > Therefore, we probably ship > `beforeinput` aligned to current Blink (this is the default behavior in > Nightly channel). And then, we should change the behavior to conform to > new Level 1, when Blink updates its behavior. Even though chang

Intent to Ship: Block HTTP ports 69, 137, 161, 1719, 1720, 1723, 6566, 10080

Hi, A couple of weeks ago, I have added the ports mentioned above to the existing list of blocked ports. The additional port blocking is in response to an improvement of last year's "NAT slipstreaming" attack, see footnote [1] for more. Again, we acknowledge that this stops an instance of the atta

Intent to ship: beforeinput event and InputEvent.getTargetRanges()

Since Nov. 2020, we enabled them by default in Nightly channel and early beta channel [1]. According to the telemetry [2], `beforeinput` events have not been used by most web apps which uses `designMode` or `contenteditable` (only 1.53%, 3k instances of `HTMLEditor`), but we know that this

Re: Intent to ship: remote-protocol (CDP)

On 12/01/2021 16:56, Anne van Kesteren wrote: On Tue, Jan 12, 2021 at 5:43 PM James Graham wrote: CDP is not part of any web standard, and is not exposed to content. Seems unfortunate we cannot standardize on this format if we have to support it anyway, but I guess that was already considered

Re: Intent to ship: remote-protocol (CDP)

On Tue, Jan 12, 2021 at 5:43 PM James Graham wrote: > CDP is not part of any web standard, and is not exposed to content. Seems unfortunate we cannot standardize on this format if we have to support it anyway, but I guess that was already considered and found not feasible? ___

Intent to ship: remote-protocol (CDP)

Summary: remote-protocol provides a Firefox implementation of a subset of the Chrome DevTools Protocol (CDP) [1], specifically targeted at testing and automation use cases. remote-protocol isn't a web-exposed feature so it doesn't fit into the standard exposure guidelines. However we're mentio

Intent to ship: Unprefixed :autofill pseudo-class, :-webkit-autofill alias.

I filed bugs[1][2] on other engines, there's explicit support from Chromium on this[3], and the relevant spec[4] and WPT[5] changes are up for review, so as soon as they're merged I plan to turn the pref on on all platforms. The bug for this is https://bugzilla.mozilla.org/show_bug.cgi?id=1685

Intent to ship: Network Partitioning

Intent to ship: Network Partitioning # Summary There are many tracking vectors that can be used by advertising networks to track users across websites. One major category of tracking vectors is known as “Supercookies,” which are stored in browsers and are difficult for users to detect and remove

Intent to ship: Setting the default referrer policy to ‘strict-origin-when-cross-origin’

Summary: Referrer-policy controls the referrer information sent in the request header. It can be specified in the response header or in the document. If no policy is specified, we use the default policy. Currently, the default is ‘no-referrer-when-downgrade’, which sends the origin, path, and quer

Intent to Ship: :focus-visible pseudo-class

Summary: Implement the :focus-visible pseudo-class and effectively make :-moz-focusring an alias of it. This is intended to simplify the way authors deal with outlines to improve accessibility. In particular, authors seem to hate outlines when users focus stuff with the mouse, generally and so

Intent to ship: PerformancePaintTiming API

/Summary: /PerformancePaintTiming API allows developers to measure the paint timing metric for their websites during pageload. /Bug/: 1518999 /Standard/: https://w3c.github.io/paint-timing/. There are two timing entries defined in spec (`first-pai

Intent to Ship: Block HTTP(s) requests to SIP ports 5060, 5061

Hi, Summary: Adding ports 5060,5061 to the existing list of blocked ports The intent for this block is to stop the specific attack of "NAT slipstreaming". We acknowledge that this stops an instance of the attack rather than solving the problem, which will happen later. Bug: 1674735 Standard:

Re: Intent to Ship: Make wheel event listeners passive by default on the root

On 10/28/20 11:18 AM, Anne van Kesteren wrote: On Mon, Oct 26, 2020 at 5:45 PM Emilio Cobos Álvarez wrote: Standard: None, this is an intervention, though https://w3c.github.io/uievents/#cancelability-of-wheel-events is loosely related. I'm not sure "it's an intervention" is sufficient reason

Re: Intent to Ship: Make wheel event listeners passive by default on the root

On Mon, Oct 26, 2020 at 5:45 PM Emilio Cobos Álvarez wrote: > Standard: None, this is an intervention, though > https://w3c.github.io/uievents/#cancelability-of-wheel-events is loosely > related. I'm not sure "it's an intervention" is sufficient reason as making breaking changes to the web platfo

Intent to Ship: Make wheel event listeners passive by default on the root

Summary: Make wheel / DOMMouseScroll / MozMousePixelScroll event listeners on the root passive by default. This effectively aligns with Chromium (see [1]), and with touchstart / touchmove events. Bug: 1673278 Standard: None, this is an intervention, though https://w3c.github.io/uievents/#ca

Re: Intent to ship: CSS conic-gradient

On Fri, Oct 9, 2020 at 12:13 PM Tim Nguyen wrote: > Summary: CSS conic-gradients allow developers to specify gradients that > start from a certain angle where color stops are placed around the > circumference of a circle centered around a specified point. > > Thanks to my friend Mohamed's work on

Intent to ship: CSS conic-gradient

Summary: CSS conic-gradients allow developers to specify gradients that start from a certain angle where color stops are placed around the circumference of a circle centered around a specified point. Thanks to my friend Mohamed's work on Direct2D

Intent to ship: Media Session API

*Summary:* Enable Media Session API by default We've enabled Media Session API on Nightly for a while, and it's time to enable it on all versions of Firefox. As of Fx82 we intend to turn Media Session API on by default on all platforms. However, on Android, this API is still not working until the

Re: Intent to ship: Implement :-moz-any() as an alias of :is()

On 9/21/20 3:46 PM, Tom Ritter wrote: I imagine there's a good reason; but I'm curious: why do we want to keep this legacy, prefixed pseudo-class and not just use is()? Removing it is generally much more risky than aliasing to something that is more permissive. This is specially true when acco

Re: Intent to ship: Implement :-moz-any() as an alias of :is()

I imagine there's a good reason; but I'm curious: why do we want to keep this legacy, prefixed pseudo-class and not just use is()? -tom On Sat, Sep 19, 2020 at 3:36 PM Emilio Cobos Álvarez wrote: > > Summary: Implement the legacy :-moz-any selector as an alias of :is(). > > This means that it'll

Intent to ship: Implement :-moz-any() as an alias of :is()

Summary: Implement the legacy :-moz-any selector as an alias of :is(). This means that it'll be more powerful, and also simpler to maintain for us. This has been enabled in 81 beta/nightly and for the whole 82 cycle with no regriessions so far, see bug 561154. This means that it will accept m

Re: Intent to ship in Nightly channel and early Beta: `beforeinput` event and `InputEvent.getTargetRanges()`

On 2020/09/18 3:13, James Graham wrote: On 17/09/2020 17:14, Masayuki Nakano wrote: web-platform-tests: none for `beforeinput` (because of it requires user input, and test driver was not when other browsers implement it), but there are a lot of tests for `getTargetRanges()` which I added (200+

Re: Intent to ship in Nightly channel and early Beta: `beforeinput` event and `InputEvent.getTargetRanges()`

On 17/09/2020 17:14, Masayuki Nakano wrote: web-platform-tests: none for `beforeinput` (because of it requires user input, and test driver was not when other browsers implement it), but there are a lot of tests for `getTargetRanges()` which I added (200+). https://searchfox.org/mozilla-central/

Intent to ship in Nightly channel and early Beta: `beforeinput` event and `InputEvent.getTargetRanges()`

Gecko is the last browser engine which does not support `beforeinput` event. The event allows web apps to cancel user input **before** updating the DOM tree, and web apps can modify the DOM tree as they need. Web apps can know what's going on with `InputEvent.inputType`, can know what's being

Intent to ship: stretching MathML operators with STIXGeneral fonts on non-mac platform

Hi, As of September 24, I intend to disable support for stretching MathML operators with the deprecated STIXGeneral fonts on non-mac platform. These are very old fonts that have been deprecated by the STIX consortium for a long time and we have been encouraging users to switch to modern fonts s

Re: Intent to ship: stretching MathML operators with STIXGeneral fonts on non-mac platform

On 17/09/2020 15:22, Frédéric Wang wrote: > Hi, > >As of September 24, I intend to disable support for stretching MathML > operators with the deprecated STIXGeneral fonts on non-mac platform. > These are very old fonts that have been deprecated by the STIX > consortium for a long time and we h

Re: Intent to ship: Update browsing context name on cross site navigation or history traversal

On Fri, Sep 11, 2020 at 10:55 PM Shuran Huang wrote: > Thanks for the pointer. I did not realize it's about the cross-origin > navigation that not switch BrowsingInstance. Just to confirm, is the case for > top-level navigation only or not? Cross-origin navigations of top-level browsing context

Re: Intent to ship: Update browsing context name on cross site navigation or history traversal

gt; https://bugs.chromium.org/p/chromium/issues/detail?id=706350. In > particular this intent to ship is about resetting window.name when the > browsing context group (aka BrowsingInstance in Chrome) is not > replaced. > > Kind regards, > > Anne Hi Anne, Thanks for the poin

Re: Intent to ship: Update browsing context name on cross site navigation or history traversal

On Fri, Sep 11, 2020 at 5:00 PM Shuran Huang wrote: > FYI, here is the tracking bug for this issue in Chrome: crbug.com/1090128. Hey Shuran, I think the bug you're looking for is https://bugs.chromium.org/p/chromium/issues/detail?id=706350. In particular this intent to ship is about r

Re: Intent to ship: Update browsing context name on cross site navigation or history traversal

On Thursday, September 10, 2020 at 8:47:37 AM UTC-4, Tim Huang wrote: > Summary: > > The window.name can persist after doing cross-origin navigation, which > means it can leak information across origins and be used as a tracking > vector. > > To address this, we want to clear the window.name when

Intent to ship: Update browsing context name on cross site navigation or history traversal

Summary: The window.name can persist after doing cross-origin navigation, which means it can leak information across origins and be used as a tracking vector. To address this, we want to clear the window.name when doing cross-origin navigations. The window.name won't persist across origins, so ca

Intent to Ship - sandbox-"allow-downloads"

Intent to Ship - sandbox-"allow-downloads" Summary: Firefox 82 will start to block downloads that are initiated by sandboxed iframes unless the embedder has opted in via setting the “allow-download” sandbox-flag. Bug: Bugzilla 1558394 <https://bugzilla.mozilla.org/show_bug.c

Intent to Ship: ::file-selector-button pseudo-element

See the original intent to implement for ::file-chooser-button here: https://groups.google.com/g/mozilla.dev.platform/c/70ODk1Gqrzs/m/CBLgePEkAAAJ I plan to rename it and enable it by default for Firefox 82 (it's enabled in Nightly / Beta only right now) as per the resolution in: https://g

Intent to ship: selectionchange for input/textarea

Summary: selectionchange for text controls has been behind the flag `dom.select_events.textcontrols.enabled`, while the behaviour was different from Chrome’s as the events fired at each element instead of `document`. I intend to modify the behaviour to make the events fire at `document` and thus fo

Re: Intent to ship: accept spaces and tabs in unquoted values (of e.g. "filename") used in Content-Disposition parameterized header pairs to to align with other browsers

Ugh. This does seem like the right thing to do in a bad situation. Thanks and thanks to Anne for working to get the spec updated. -Ekr On Wed, Aug 19, 2020 at 10:10 AM Gijs Kruitbosch wrote: > It's been pointed out to me that I neglected to merge the "intent to > prototype" requirements into my

Re: Intent to ship: accept spaces and tabs in unquoted values (of e.g. "filename") used in Content-Disposition parameterized header pairs to to align with other browsers

It's been pointed out to me that I neglected to merge the "intent to prototype" requirements into my email. So: Platform coverage: everywhere. Preference: no pref. DevTools bug: covered by existing network tooling (it already shows the full header). Other browsers: as noted, they already do th

Intent to ship: accept spaces and tabs in unquoted values (of e.g. "filename") used in Content-Disposition parameterized header pairs to to align with other browsers

As of Firefox 81 I intend to update our parsing of Content-Disposition headers so that spaces/tabs in unquoted values are treated as part of the value (rather than as a separator, cutting off the value). This is what Blink and Webkit already do. Bug for this change: https://bugzilla.mozilla.or

Intent to ship: selectionchange for input/textarea

Summary: selectionchange for text controls has been behind the flag `dom.select_events.textcontrols.enabled`, while the behaviour was different from Chrome’s as the events fired at each element instead of `document`. I intend to modify the behaviour to make the events fire at `document` and thus

Intent to ship: Redirect Tracking Protection (formerly ETP Cookie Purging)

As of July 28th we've started a slow rollout of redirect tracking protection feature (which we've previously called "ETP Cookie Purging") in Firefox 79 Desktop. We’ve started with 1% of users and will slowly increase over the coming weeks. The feature is behind the privacy.purge_trackers.enabled pr

Intent to ship: CSS overflow:clip

Summary: We intend to ship CSS overflow:clip in v81, which is the standardized version of a prefixed value (-moz-hidden-unscrollable) that we already ship. The prefixed value becomes an alias for the new value. The standardized value is mostly compatible, but there are some differences. Most not

Re: Intent to ship: WebAssembly bulk-memory-operations and reference-types proposals

Dana Bishop ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Intent to ship: Javascript `export * as ns from "mod";` syntax

Hi, In Firefox 80, we'll ship the `export * as ns from "mod";` JavaScript syntax. *Bug: *https://bugzilla.mozilla.org/show_bug.cgi?id=1496852 *Standard: *https://github.com/tc39/ecma262/pull/1174 *Platform coverage: *All, no pref *DevTools bug: *N/A. *Other browsers: *Shipping in Chrome *Testing

Intent to ship: unprefixed appearance property

I intend to land bug 1620467 tomorrow, which implements the unprefixed appearance property and removes many non-standard values of -moz-appearance. Intent to Prototype mail: https://groups.google.com/g/mozilla.dev.platform/c/nlun5QV63Bo/m/xUXCmySGAgAJ The only things that have changed since tha

Intent to ship: Animation composite modes

to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/Wu4yPMznUw0/m/lgikzszpAwAJ ). Safari have not announced concrete plans to ship this but have shown positive signals. Product: n/a Bug to turn on by default: https://bugzilla.mozilla.org/show_bug.cgi?id=1652676 There is no intent to

Re: Intent to ship: returning shared memory to the web

I want to add that enabling shared memory in Firefox also enables wasm thread operations [1]. That proposal is only at stage 2 in the Community Group, but has been in Chrome release since v74, is used in live content on the web (eg Google Earth), and is therefore in its final form for all practica

Re: Intent to Ship : HTML5 element (Nightly Only)

I think it should be returned to the element > which had focus before the dialog was shown, which is the recommended > pattern for good accessibility of dialogs. I don't think there is a spec > issue for this yet. > > Jamie > > On Thu, Jun 25, 2020 at 6:04 AM Sean Feng wrote: >

Intent to ship: WebAssembly bulk-memory-operations and reference-types proposals

Hi all, In bug 1528294 and bug 1637884 I intend to ship the WebAssembly bulk-memory-operations and reference-types proposals. The bulk-memory-operations proposal adds new instructions for common data manipulation operations such as 'memcpy' and 'memset'. WebAssembly code using these instructions

Re: Intent to Ship : HTML5 element (Nightly Only)

element which had focus before the dialog was shown, which is the recommended pattern for good accessibility of dialogs. I don't think there is a spec issue for this yet. Jamie On Thu, Jun 25, 2020 at 6:04 AM Sean Feng wrote: > Intent to Ship (Nightly Only) : Dialog Element >

Intent to Ship : HTML5 element (Nightly Only)

Intent to Ship (Nightly Only) : Dialog Element ​ Hi All, ​ In bug 1645046 <https://bugzilla.mozilla.org/show_bug.cgi?id=1645046>, I intend to turn html5 element on by default in Nightly. It has been developed behind the dom.dialog_element.enabled preference. ​ Meta Tracking Bug:

Intent to ship: returning shared memory to the web

At the end of August 2019 we expressed an intent to prototype the re-enablement of SharedArrayBuffer[1]. Many bugs and design iterations later, we’re happy to announce that it’s now ready. We would like to ship this in Firefox 79 or 80. To do this in a post-Spectre-safe manner we have worked with

Re: Intent To Ship: backdrop-filter

On Tuesday, June 9, 2020 at 3:01:23 PM UTC-7, L. David Baron wrote: > On Friday 2020-05-29 12:50 -0700, Erik Nordin wrote: > > Intent: > > > > As of Nightly 79 (shipping in release 7/28) I intend to turn > > backdrop-filter on by default for all systems on which WebRender is enabled. > > > > Here

Re: Intent To Ship: backdrop-filter

One other note: I don't think we should be too concerned about the specific multiple-graphics-backends situation arising frequently in the future. The goal is to have a single backend (WebRender) going forward, and last I checked the plan was to completely drop all other backends within the next 12

Re: Intent To Ship: backdrop-filter

Thanks David and Martin for the feedback on this proposal. I'll try to address the various questions and concerns below: To that end, is there a plan for making this capability uniformly available? > We don't have any plans to implement backdrop-filter on other graphics backends. This property ha

Re: Intent To Ship: backdrop-filter

On Wed, Jun 10, 2020 at 8:01 AM L. David Baron wrote: > It's also something that I think we shouldn't be doing, at least not > without a clear and relatively short timeline for having the feature > available across all graphics backends (whether by implementing it > for more backends or by no long

Re: Intent To Ship: backdrop-filter

On Friday 2020-05-29 12:50 -0700, Erik Nordin wrote: > Intent: > > As of Nightly 79 (shipping in release 7/28) I intend to turn > backdrop-filter on by default for all systems on which WebRender is enabled. > > Here is a list of systems and their current status with regard to shipping > WebRender

Re: Intent to Ship: Require user interaction for session history entries

I didn't initially add it to Fenix/GV because I wanted to keep the bug focused on the session history pieces and also wanted to give the mobile team a chance to evaluate this independently (the back button might work slightly differently on mobile). As mentioned, it should in theory be easy to add

Re: Intent to Ship: Require user interaction for session history entries

On Tuesday, June 9, 2020 at 2:17:02 PM UTC-7, Johann Hofmann wrote: > In bug 1515073 I > plan to land an intervention that is aimed to reduce user frustration from > an issue with malfunctioning or malicious websites which is commonly known > a

Intent To Ship: backdrop-filter

Intent: As of Nightly 79 (shipping in release 7/28) I intend to turn backdrop-filter on by default for all systems on which WebRender is enabled. Here is a list of systems and their current status with regard to shipping WebRender: https://wiki.mozilla.org/Platform/GFX/WebRender_Where The featu

Intent to Ship: Require user interaction for session history entries

In bug 1515073 I plan to land an intervention that is aimed to reduce user frustration from an issue with malfunctioning or malicious websites which is commonly known as the “broken back button”. For user-initiated session history interactions

Intent to ship: JavaScript weak references

This week JS weak refs will be enabled on nightly and will ride the trains, ultimately shipping in Firefox 79. It has been developed behind the javascript.options.experimental.weakrefs preference (which will be renamed to javascript.options.weakrefs). Status in other browsers: - Chrome: will sh

Re: Intent to ship: ParentNode#replaceChildren

Yes: https://github.com/web-platform-tests/wpt/blob/master/dom/nodes/ParentNode-replaceChildren.html On Tuesday, May 26, 2020 at 1:51:13 PM UTC-7, James Graham wrote: > On 25/05/2020 16:45, Alex Vincent wrote: > > Effective 2020-05-27, I intend to land ParentNode.replaceChildren feature > > in mo

Re: Intent to ship: ParentNode#replaceChildren

On 25/05/2020 16:45, Alex Vincent wrote: Effective 2020-05-27, I intend to land ParentNode.replaceChildren feature in mozilla-central, on by default. This has not been developed behind a preference, as both I and the reviewers believe this is a small change. Status in other browsers is unimplemen

Intent to ship: ParentNode#replaceChildren

Effective 2020-05-27, I intend to land ParentNode.replaceChildren feature in mozilla-central, on by default. This has not been developed behind a preference, as both I and the reviewers believe this is a small change. Status in other browsers is unimplemented. *Product*: N/A *Bug to turn on by def

Intent to Ship: and Link: rel=preload support on Nightly and Early Beta

** Summary ** "" HTML tag and "Link: rel=preload" HTTP response header are a web technology allowing web developers to tell the browser to early load and pre-cache resources that will be used by the currently loading web page, specifically scripts, stylesheets, images, fonts and fetch (for `fe

Intent to ship: "JS BigInt to I64 integration" WebAssembly proposal

# Intent to ship: "JS BigInt to I64 integration" WebAssembly proposal This feature allows I64 values in WebAssembly to be exported to JavaScript as a BigInt value, or imported from JS from a BigInt. With this proposal implemented, all four value types in the WebAssembly MVP can be pass

Intent to ship: "JS BigInt to I64 integration" WebAssembly proposal

# Intent to ship: "JS BigInt to I64 integration" WebAssembly proposal This feature allows I64 values in WebAssembly to be exported to JavaScript as a BigInt value, or imported from JS from a BigInt. With this proposal implemented, all four value types in the WebAssembly MVP can be pass

Re: Intent to ship: :read-only / :read-write pseudo-classes

A clarification given this came up in chat.mozilla.org: I'm keeping the support for parsing the old prefixed versions for backwards compat, aliased to the un-prefixed ones. We can potentially remove them, but probably at another time, specially given we're trying to minimize deprecations / bre

Intent to ship: :read-only / :read-write pseudo-classes

*Summary: *Make our :-moz-read-only / :-moz-read-write pseudo-classes match the spec, and un-prefix them. *Bug: *Bug 312971 *Standard: *https://html.spec.whatwg.org/#selector-read-only // *Platform coverage: *All *

Intent to ship: RegExp dotAll flag (/s), unicode escape sequences, lookbehind assertions

As of Firefox 78, we will ship an updated version of the regexp engine, which will support dotAll, unicode property escapes, and lookbehind assertions. Use case: The dotAll flag allows `.` in regular expressions to match any character, including newlines. Unicode property escapes can be used

Intent to Ship: inputmode attribute on Android (GeckoView)

inputmode attribute is a hint to adjust software keyboard layout (numeric, email and etc). Originally this attribute was implemented by B2G, but this was still disabled on beta and release channel. Although we also support this attribute on GeckoView, Windows and Linux/GTK3 (macOS doesn't have soft

Re: Intent to ship: a change to the initial value of image-orientation

On Mon, Feb 17, 2020, at 8:19 AM, Cameron McCormack wrote: > This doesn't really fit the format of an Intent email, but just as a > heads up, I am landing a change to the initial value of the > image-orientation property, from "none" to "from-image". The effect of > this change is that EXIF ori

Intent to ship: Logical Assignment for JavaScript

We recently implemented Logical Assignment in SpiderMonkey. The proposal gives programmers a shorthand for logical assignment. André Bargull [:anba] contributed the patches that implemented this proposal. It landed in Nightly this week. We'll ship it once we're confident the specification is stabl

Intent to ship: AudioWorklet

As of this week I intend to turn on AudioWorklet by default for all platforms. It has been developed behind the "dom.audioworklet.enabled" and "dom.worklet.enabled" preferences. Status in other browsers is: Chrome, Opera: shipping. Edge, Webkit: not shipping, intentions unknown. Product: Adam St

Intent to ship: "Multi-value" WebAssembly proposal

# Intent to ship: "Multi-value" WebAssembly proposal This feature adds support for WebAssembly functions that return multiple values and receive multiple return values, including across the JS/wasm call boundary. The multi-value feature also adds support for multiple results from &

Intent to ship: Atomics and SharedArrayBuffer objects (limited to a single thread)

Hi, Planned for Firefox 78. Summary: This is a small but important step in returning shared memory support to the web. The postMessage() API throws and will continue to throw when given a SharedArrayBuffer object so this specific change does not give developers shared memory, but it does return

Intent to ship: -less RDM

Hi all, Later this week, we’ll be enabling a new version of the Responsive Design Mode tool that no longer relies on as part of the initiative to make DevTools Fission-compatible. For now, the pref will only be enabled in Firefox Nightly as we work with QA to ensure the stability of the tool. Th

  1   2   3   4   5   6   7   8   9   10   >