W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2013

Re: [whatwg] HTML Specification update request: bug 20939

From: Bob Owen <bobowencode@gmail.com>
Date: Fri, 8 Mar 2013 12:56:16 +0000
Message-ID: <CA+dJEECdC-SYgrZwPQiZJx7f05kDk-55kCD+2uBF4ZtSD2TPfQ@mail.gmail.com>
To: whatwg@whatwg.org
Hi,

Has anyone had a chance to look at my proposals to improve the HTML
specification with regard to navigating browsing contexts while sandboxed?

Thanks,
Bob


Message: 3

> Date: Sat, 9 Feb 2013 16:26:12 +0000
> From: Bob Owen <bobowencode@gmail.com>
> To: whatwg@whatwg.org
> Subject: [whatwg] HTML Specification update request: bug 20939
> Message-ID:
>         <
> CA+dJEEDvYM+HKC9vvNF70PXYxz7ATiBdoSmfiFNCXxWyg-u2FQ@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> While discussing with Boris Zbarsky, some work I am doing on sandboxing for
> Mozilla, we realised that the sections in the HTML specification on
> browsing context security and browsing context names, could do with some
> clarification with regard to the effects of sandboxing.
>
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#security-nav
>
> http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#browsing-context-names
>
> The non-normative table, in the browsing context names section, does cover
> many of the effects.
> However, if the normative text in these two sections is read on its own,
> without knowledge of the sandboxing sections, then the reader could easily
> come away with an incorrect understanding.
>
> I have raised the following bug detailing all of this.
>
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=20939
>
> The bug also contains some suggestions for new rows that could be added to
> the non-normative table.
>
> Thanks,
> Bob
>
>
>
Received on Friday, 8 March 2013 12:56:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 8 March 2013 12:56:43 GMT