<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>74819</bug_id>
          
          <creation_ts>2011-12-18 13:15:31 -0800</creation_ts>
          <short_desc>Remove document.charset and document.defaultCharset</short_desc>
          <delta_ts>2011-12-22 11:01:34 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>DOM</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Anne van Kesteren">annevk</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>ap</cc>
    
    <cc>Ms2ger</cc>
    
    <cc>sam</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>523522</commentid>
    <comment_count>0</comment_count>
    <who name="Anne van Kesteren">annevk</who>
    <bug_when>2011-12-18 13:15:31 -0800</bug_when>
    <thetext>Gecko only supports document.characterSet and that is the one DOM4 will keep. The others will be removed from the standard as they do not seem necessary for legacy compatibility.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>524648</commentid>
    <comment_count>1</comment_count>
    <who name="Alexey Proskuryakov">ap</who>
    <bug_when>2011-12-20 09:24:48 -0800</bug_when>
    <thetext>Document.defaultCharset is not an alias for charset, so let&apos;s not discuss it here. Perhaps you meant inputEncoding? If you&apos;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 &lt;http://www.w3.org/TR/REC-DOM-Level-1/level-one-html.html&gt; and &lt;http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-inputEncoding&gt; 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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>526208</commentid>
    <comment_count>2</comment_count>
    <who name="Anne van Kesteren">annevk</who>
    <bug_when>2011-12-22 05:50:38 -0800</bug_when>
    <thetext>I meant document.charset and document.defaultCharset, neither of which is listed in either of the documents you cite.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>526371</commentid>
    <comment_count>3</comment_count>
    <who name="Alexey Proskuryakov">ap</who>
    <bug_when>2011-12-22 11:01:34 -0800</bug_when>
    <thetext>My mistake, charset is not in any W3C spec indeed. Still, it&apos;s supported in vast majority of browsers, and removing support from WebKit would be counter-productive.

If you actually meant defaultCharset, then why did you report both in the same bug? It&apos;s a completely different feature.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>