On Thu, Feb 21, 2019 at 9:56 AM L. David Baron wrote:
> On Thursday 2019-02-21 15:44 +0100, Andy Wingo wrote:
> > ## Support in other browser / JS engines
> >
> > Chrome / V8 implements the draft spec.
> >
> > Safari / JavaScriptCore has a partial implementation that is being
> > completed on an
Am Donnerstag, 21. Februar 2019 20:57:02 UTC+1 schrieb David Baron:
> Have either of them announced plans to ship (or actually shipped)
> this feature?
https://www.chromestatus.com/features/5371603852460032
___
dev-platform mailing list
dev-platform@list
I talked to peterv about the pdf.js issues this morning, and the general
consensus is that fake plugins were seen as "a way" to fix those issues but
not a definite solution. Also, it had been for a while since any of that
was even discussed and no one had approached the problem, so removing fake
pl
On 2/17/19 11:40 PM, Henri Sivonen wrote:
> Rust, which combines the
> perf benefits of -fstrict-aliasing with the understandability of
> -fno-strict-aliasing?
This is not really true of Rust. Rust's memory model is not really defined yet
https://doc.rust-lang.org/reference/memory-model.html but
On 2/21/19 11:56 AM, L. David Baron wrote:
> (What's the opinion of TC39 on shipping features that are at stage
> 3? That doesn't seem obvious from
> https://tc39.github.io/process-document/ .)
Stage 3 is traditionally where it becomes okay to ship stuff, and it's the
usual dividing line we have
On 2/21/19 3:44 PM, Kyle Machulis wrote:
and Pdf.js is still shipping as a stream handler for the
time being.
Note that there are a bunch of issues with that (e.g. around
window.print()), which we were hoping fake plugins would solve. If that
plan has been abandoned, it might be worth findin
Metabug: https://bugzilla.mozilla.org/show_bug.cgi?id=1529133
Fake plugins are JS plugins that render as a document instead of a plugin,
but still live in the general area of plugins (loading through object/embed
elements in nsObjectLoadingContent, having plugin tags, etc). They were
original crea
On Thursday 2019-02-21 15:44 +0100, Andy Wingo wrote:
> ## Support in other browser / JS engines
>
> Chrome / V8 implements the draft spec.
>
> Safari / JavaScriptCore has a partial implementation that is being
> completed on an ongoing basis by Caio Lima.
Have either of them announced plans to
# Intent to ship: BigInt
This feature adds support for arbitrary-precision integers to the
JavaScript language. BigInt values are a new kind of primitive. The
usual arithmetic operations are extended to work on BigInt values. As
specified, arithmetic operations between BigInt and Number values
9 matches
Mail list logo
