I support this recharter (disclaimer: I'm a co-chair so of course I do).
-Dan Veditz
On Fri, Feb 22, 2019 at 5:29 PM L. David Baron wrote:
> The W3C is proposing a revised charter for:
>
> Web Application Security (WebAppSec) Working Group
> https://www.w3.org/2019/02/webappsec-2019-proposed
The W3C is proposing a revised charter for:
Web Application Security (WebAppSec) Working Group
https://www.w3.org/2019/02/webappsec-2019-proposed-charter.html
https://lists.w3.org/Archives/Public/public-new-work/2019Feb/0010.html
Mozilla has the opportunity to send comments or objections th
On 2/22/19 4:14 PM, Boris Zbarsky wrote:
There is a certain amount of compat risk here, since this is changing a
very longstanding behavior. I'm hoping that by aligning with the spec
(except for a few edge cases like calling document.open() on a document
whose iframe has been removed from the
On 22/02/2019 22:14, Boris Zbarsky wrote:
All the "wyciwyg" bits in the tree are being removed in the process.
\o/
~ Gijs
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Summary: historically in Gecko document.open created a new global and
new session history entry (unless "replace" was passed). We also stored
the written data in a "wyciwyg" cache entry so it could participate
meaningfully in session history. I plan to change these behaviors and
simplify the
Summary: We plan to place multiple globals in a single compartment to
reduce the memory overhead due to cross-compartment wrappers and the
performance overhead of traversing those wrappers. Globals will be
placed in the same compartment if: (1) they are same-origin (ignoring
document.domain) a
On Fri, Feb 22, 2019 at 1:00 AM Jeff Walden wrote:
>
> 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 defin
7 matches
Mail list logo
