[Bug 27436] Document.charset

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27436

--- Comment #6 from Henri Sivonen <hsivonen@hsivonen.fi> ---
What does the setter do?

Is it known that if the property sniffs as existing, sites won't try to use the
setter (i.e. having it as getter-only would be safe)?

(In reply to Anne from comment #3)
> If
> different casing needs to be considered (note that browsers do not
> consistently use uppercase or lowercase today)

Didn't WebKit make a specific effort to be consistent with Gecko's (rather
arbitrary) casing? Have you researched why the WebKit developers made the
effort to be case-consistent with Gecko?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 26 November 2014 13:47:16 UTC