> 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 l
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%
> https://www.chromestatus.com/metrics/feature/timeline/popularity/480
>
> (f
On 11/19/15 6:57 PM, Jonas Sicking wrote:
You can actually create a MessageChannel and then send one of the
ports to a sub-sub-worker.
Ah, good point.
Unfortunately the other port can't be used as something that
represents the sub-sub-worker since even after a port has started
getting used, i
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 below 0.03%)
hope it
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
On Fri, Nov 20, 2015 at 11:05:58AM +1100, Xidorn Quan wrote:
> That's a great news. Hopefully Windows builds would no longer be a
> significant backlog anymore.
The backlog usually was for tests, not builds.
Mike
___
dev-platform mailing list
dev-platfo
That's a great news. Hopefully Windows builds would no longer be a
significant backlog anymore.
On Fri, Nov 20, 2015 at 7:23 AM, 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 anno
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 tags has been widely used on the web.
>
> T
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 sub-sub-worker.
>
> While true
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 like
https://drafts.c
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
sub-sub-work
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.
It also doesn't seem possible for a worker to convert to the timeline
of a parent window, since there's no object representi
Summary: A new method on Performance that allows translating a timestamp
from one timeline to another. The idea is that you can take a
performance.now() value or performance mark from some other global and
convert them to the timeline of your global. It works like this:
var myTime = Perfor
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
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 W
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 Windo
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 wrote:
> Summary:
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 examp
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 Nightly and Developer builds
19 matches
Mail list logo
