Intent to Prototype: text-decoration-skip-ink

2019-08-06 Thread Charlie Marlow
Summary: text-decoration-skip-ink is a CSS feature that makes underlines and overlines skip around the text, instead of painting behind it. There is a picture of this effect on the standards link. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1411922

[intent to deploy] Changes to show_bug.cgi on BMO

2019-08-06 Thread Emma Humphries
Hello, Kohei's finishing up some changes to how information is organized in show_bug.cgi, and we'd like your feedback before we deploy it. The enhancement bug for this work is: https://bugzilla.mozilla.org/show_bug.cgi?id=1344091 You can see this work previewed on

Planned Taskcluster Migration Upcoming

2019-08-06 Thread Dustin Mitchell
*tl;dr:* Taskcluster, the platform supporting Firefox CI, will be moving to a new hosting environment during the tree-closing window at the end of September. This is a major change and upgrade to the platform, but may cause some bumps along the way. Taskcluster is in the midst of a few

Re: Intent to ship: accumulating most JS scripts' data as UTF-8, then directly parsing as UTF-8 (without inflating to UTF-16)

2019-08-06 Thread Jeff Walden
On 8/6/19 8:16 AM, Anne van Kesteren wrote: > On Sat, Jul 20, 2019 at 2:05 AM Jeff Walden wrote: >> (*Only* valid UTF-8: any invalidity, including for WTF-8, is an immediate >> error, no replacement-character semantics applied.) > > Wouldn't adding this allow you to largely bypass the text

Re: Non-header-only headers shared between SpiderMonkey and the rest of Gecko

2019-08-06 Thread Kris Maglione
On Tue, Aug 06, 2019 at 10:56:55AM +0300, Henri Sivonen wrote: Do we have some #ifdef for excluding parts of mfbt/ when mfbt/ is being used in a non-SpiderMonkey/Gecko context? #ifdef MOZ_HAS_MOZGLUE ___ dev-platform mailing list

Re: Intent to ship: accumulating most JS scripts' data as UTF-8, then directly parsing as UTF-8 (without inflating to UTF-16)

2019-08-06 Thread Anne van Kesteren
On Sat, Jul 20, 2019 at 2:05 AM Jeff Walden wrote: > (*Only* valid UTF-8: any invalidity, including for WTF-8, is an immediate > error, no replacement-character semantics applied.) Wouldn't adding this allow you to largely bypass the text decoder if it identifies the content to be UTF-8?

Re: Non-header-only headers shared between SpiderMonkey and the rest of Gecko

2019-08-06 Thread Henri Sivonen
On Tue, Aug 6, 2019 at 10:15 AM Henri Sivonen wrote: > In general, it seems problematic to organize headers based on whether > they have associated .cpp or crate code. I'd expect developers to look > for stuff under mfbt/ instead of some place else, since developers > using the header shouldn't

Re: Non-header-only headers shared between SpiderMonkey and the rest of Gecko

2019-08-06 Thread Henri Sivonen
On Mon, Aug 5, 2019 at 4:14 PM Gabriele Svelto wrote: > On 05/08/19 12:04, Henri Sivonen wrote: > > I has come to my attention that that putting non-header-only code > > under mfbt/ is something we're trying to get away from: > > https://bugzilla.mozilla.org/show_bug.cgi?id=1554062 > > > > Do we