Re: Intent to ship: unicode-range

On Thu, Nov 19, 2015 at 5:16 PM, John Daggett wrote: > We intend to ship unicode-range in Firefox 44. It has been implemented for > non-Linux platforms for over a year now behind the > "layout.css.unicode-range.enabled" pref. The pref has been enabled by > default for

Intent to Implement: HTML and tags

Summary: The is used as a disclosure widget from which the user can obtain additional information or controls. is used as a summary or legend of the details. To expand the details, the user could click on the summary or by adding a bool attribute 'open' to the details. An example: Open the

Re: Intent to Implement: HTML and tags

I'll give the same feedback here as I did for . I don't think authors will use this very much unless they can style it. In this case enabling styling might not actually be that hard either, so especially worth looking into. / Jonas On Thu, Nov 19, 2015 at 1:21 AM, Ting-Yu Lin

Faster Windows builds on Try

Over the past months we've been working on migrating our Windows builds from the legacy hardware machines into Amazon. I'm very happy to announce that we've wrapped up the initial work here, and all our Windows builds on Try are now happening in Amazon. The biggest win from this is that our

Re: Intent to Implement: HTML and tags

On Thu, Nov 19, 2015 at 3:05 PM, Xidorn Quan wrote: > On Fri, Nov 20, 2015 at 6:22 AM, Jonas Sicking wrote: >> I'll give the same feedback here as I did for . >> >> I don't think authors will use this very much unless they can style it. > > This pair of

Re: Intent to Implement: HTML and tags

On Thursday 2015-11-19 11:22 -0800, Jonas Sicking wrote: > I'll give the same feedback here as I did for . > > I don't think authors will use this very much unless they can style it. There are some styling mechanisms in other browsers, but I don't think they are standardized, and I don't know if

Re: Intent to implement and ship: Performance.translateTime

On Thu, Nov 19, 2015 at 2:48 PM, Boris Zbarsky wrote: > On 11/19/15 5:39 PM, Jonas Sicking wrote: >> >> This API doesn't seem to work for nested workers (which Blink doesn't >> implement), does it? Since there's no way in the window to get hold of >> a reference of a

Re: Intent to Implement: HTML and tags

Jonas, Le 20 nov. 2015 à 04:22, Jonas Sicking a écrit : > I don't think authors will use this very much unless they can style it. DetailsElement - 0.0856% https://www.chromestatus.com/metrics/feature/timeline/popularity/480 (features are at risk of removal for Chrome when

Re: Faster Windows builds on Try

This is the greatest! Thank you so much! On 19/11/2015 3:23 PM, Chris AtLee wrote: > Over the past months we've been working on migrating our Windows builds > from the legacy hardware machines into Amazon. > > I'm very happy to announce that we've wrapped up the initial work here, and > all our

Intent to implement and ship: Changes to Worker performance.now() zero time

Summary: Currently for a dedicated worker, we set its 0 time for performance.now() purposes to the zero time of its parent worker or window. The spec defines a different behavior, now that there is a spec for this. Consumers that rely on the timebases matching right now can use translateTime

Re: Intent to Implement: HTML and tags

On Fri, Nov 20, 2015 at 6:22 AM, Jonas Sicking wrote: > I'll give the same feedback here as I did for . > > I don't think authors will use this very much unless they can style it. This pair of tags has been widely used on the web. The first example is experimental CSS specs

Re: Intent to implement and ship: Performance.translateTime

On 11/19/15 5:39 PM, Jonas Sicking wrote: This API doesn't seem to work for nested workers (which Blink doesn't implement), does it? Since there's no way in the window to get hold of a reference of a sub-sub-worker. While true, there is also no way to directly get a message from a

Re: Intent to ship: unicode-range

> One question that, the current nightly is Firefox 45, and I suppose > you are not going to uplift the enabling bug, so you probably meant > shipping in Firefox 45? Plan is to uplift to aurora, so Firefox 44 is the intent. ​ ​ ___ dev-platform mailing

Re: Intent to Implement: HTML and tags

On Thu, Nov 19, 2015 at 5:33 PM, Karl Dubost wrote: > Jonas, > > Le 20 nov. 2015 à 04:22, Jonas Sicking a écrit : > > I don't think authors will use this very much unless they can style it. > > DetailsElement - 0.0856% >