2013/8/1 Ian Hickson :
> On Thu, 1 Aug 2013, Martin Janecke wrote:
>>
>> I don't see any sense in making a document that is declared as
>> ISO-8859-1 and encoded as ISO-8859-1 non-conforming. Just because the
>> ISO-8859-1 code points are a subset of windows-1252? So is US-ASCII.
>> Should an US-AS
On Sat, Aug 3, 2013 at 1:29 AM, Mohammad Al Houssami (Alumni)
wrote:
> If you go to http://livedom.validator.nu/ and try to add the DOM tree
> shows the head and body elements. I am using this as a reference to compare
> to my results. Its not reliable then?
I... don't understand what you're a
Le 03/08/2013 16:02, Boris Zbarsky a écrit :
On 8/3/13 9:48 AM, David Bruant wrote:
"a.example.org" can sandbox the iframe to "b.example.org" and process
isolation becomes possible again
Yes, agreed. This might be a good idea. It just has nothing to do
with protecting one from attacks by th
On 8/3/13 9:48 AM, David Bruant wrote:
"a.example.org" can sandbox the iframe to "b.example.org" and process
isolation becomes possible again
Yes, agreed. This might be a good idea. It just has nothing to do with
protecting one from attacks by the other in general, because they can
use wind
Le 03/08/2013 03:03, Boris Zbarsky a écrit :
On 8/2/13 6:44 PM, David Bruant wrote:
And apparently @sandbox doesn't help here if there is allow-same-origin.
So here is an idea: make the document.domain setter throw inside an
iframe@sandbox, *regardless* of allow-same-origin. That solves the
mail
If you go to http://livedom.validator.nu/ and try to add the DOM tree
shows the head and body elements. I am using this as a reference to compare to
my results. Its not reliable then?
Thank you
-Original Message-
From: Tab Atkins Jr. [mailto:jackalm...@gmail.com]
Sent: Saturday, Augus
