Intent to implement: scroll-boundary-behavior

Summary: A CSS property that allows web developers to control what scroll boundary actions performed by the browser (such as scroll handoff to a parent scrollable element, visual overscroll effect, swipe navigation, etc.) should apply to a scrollable element. Tracking bug:

[Firefox Desktop] Issues found: October 16th to October 20th

Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *October 16 - October* *20*  (week 42). Additional details on the team's priorities last week, as well as the plans for the current week are available at:

Move assignment and constructors for ns[C]String

Hello everyone! Bug 1377351 landed on central recently, and adds move assignment operators and constructors to ns[C]String. These operators attempt to re-use allocations when possible and can reduce the cost of copying strings around. This could be used in some situations to improve assignment

Re: De-XBL Plans

> On Oct 22, 2017, at 3:35 AM, smaug wrote: > > On 10/21/2017 11:45 PM, Yura Zenevich wrote: >> I would also like to bring to the team's attention another force worth >> being on the radar (in terms of "forces on the system") - accessibility. >> One theme that seems to

Re: Threadsafe URLs - MozURL

On 10/23/17 10:30 AM, Jeff Muizelaar wrote: For the curious among us, what made nsIURI not thread safe in the first place? There were several aspects to this: 1) Constructing a URI object. This needed a protocol handler, which could be implemented in JS by extensions. With XPCOM

Re: Threadsafe URLs - MozURL

On 23 October 2017 at 16:21, Anne van Kesteren wrote: > On Mon, Oct 23, 2017 at 4:01 PM, Valentin Gosu > wrote: > > A few weeks ago we landed MozURL. This is an immutable threadsafe wrapper > > for rust-url. > > What is the plan for these issues: > >

Re: Threadsafe URLs - MozURL

On 23 October 2017 at 16:30, Jeff Muizelaar wrote: > For the curious among us, what made nsIURI not thread safe in the first > place? > One of the factors was that as an IDL nsIURI could also be implemented by JS code in addons, which could only run on the main thread.

Re: Threadsafe URLs - MozURL

For the curious among us, what made nsIURI not thread safe in the first place? -Jeff On Mon, Oct 23, 2017 at 10:01 AM, Valentin Gosu wrote: > Hi everyone, > > Threadsafe URLs have been high on everybody's wishlist for a long while. > The fact that our nsIURI

Re: Threadsafe URLs - MozURL

On Mon, Oct 23, 2017 at 4:01 PM, Valentin Gosu wrote: > A few weeks ago we landed MozURL. This is an immutable threadsafe wrapper > for rust-url. What is the plan for these issues: https://github.com/servo/rust-url/issues/163

Threadsafe URLs - MozURL

Hi everyone, Threadsafe URLs have been high on everybody's wishlist for a long while. The fact that our nsIURI implementations weren't thread safe meant that hacks had to be used to use a URI off the main thread, such as saving it as a string, or bouncing back to the main thread whenever you had

Intent to implement: DevTools onboarding page

# Summary When users try to open DevTools for the very first time, we would like to prompt them for a confirmation first, displayed in an onboarding page. The main goal is to inform new users about DevTools, and avoid accidental or malicious usage. A secondary goal is performance related. Some

Re: How can I get SOCKS settings params of Firefox?

I don't know how well GConf is supported by more recent GNOME versions. I assume GSettings support was added to nsUnixSystemProxySettings because GConf was to be no longer supported, but the crash reporter uses separate code. https://bugzilla.mozilla.org/show_bug.cgi?id=1388897