[Webkit-unassigned] [Bug 74819] Remove document.charset and document.defaultCharset

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Dec 20 09:24:48 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=74819


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #1 from Alexey Proskuryakov <ap at webkit.org>  2011-12-20 09:24:48 PST ---
Document.defaultCharset is not an alias for charset, so let's not discuss it here. Perhaps you meant inputEncoding? If you'd actually like us to consider removing defaultCharset, please file a separate bug, although my initial answer will be similar to the one below.

Both document.charset and document.inputEncoding are well established in standards, and should not be removed from implementations. See <http://www.w3.org/TR/REC-DOM-Level-1/level-one-html.html> and <http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-inputEncoding> respectively.

I would suggest the following course of action: specify all of charset, characterSet and inputEncoding, the latter two being deprecated. Document.charset is writable, and that trait can also be deprecated as far as I know, but it needs research. Implementations will not remove support for any of these in foreseeable future.

The reason why I suggest making charset the non-deprecated one is that it has the longest history in major browsers, and is best known to web developers.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list