W3C home > Mailing lists > Public > public-webappsec@w3.org > July 2016

Re: Changing window.name behavior

From: Mike West <mkwst@google.com>
Date: Tue, 19 Jul 2016 10:12:31 +0200
Message-ID: <CAKXHy=cxyYUtnbiLi2_J3k_-LtePKyDgZ7+jNJ9qs7MfGEPSgQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: Dan Anderson <dan-anderson@cox.net>, John Wilander <wilander@apple.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
https://www.iab.com/wp-content/uploads/2014/08/SafeFrames_v1.1_final.pdf
came to my attention this morning. Section 2.4 outlines the way it uses `
window.name` to serialize "configuration attributes of: a particular
SafeFrame position configuration, metadata, and the content to be
rendered" across origins.

Like it or not, it would probably be a good idea to make sure we're not
breaking this ad delivery system without thinking about it first. :)

-mike

On Mon, Jul 18, 2016 at 9:18 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> On Thu, Jul 7, 2016 at 9:11 PM, Dan Anderson <dan-anderson@cox.net> wrote:
> > Maybe open a bug report for the browsers that are not following the
> specs?
> >
> > I think there was one for Mozilla once.
>
> See https://bugzilla.mozilla.org/show_bug.cgi?id=444222. I think we
> basically lack someone to work on it...
>
>
> --
> https://annevankesteren.nl/
>
>
Received on Tuesday, 19 July 2016 08:13:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:20 UTC