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

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>27161</bug_id>
          
          <creation_ts>2014-10-24 18:14:53 +0000</creation_ts>
          <short_desc>[editorial] make data URL in iframe conform to requirements in URL spec</short_desc>
          <delta_ts>2014-11-27 09:17:58 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WHATWG</product>
          <component>HTML</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc>https://html.spec.whatwg.org/multipage/embedded-content.html#best-practices-for-metadata-text-tracks</bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>Unsorted</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Michael[tm] Smith">mike</reporter>
          <assigned_to name="Ian &apos;Hixie&apos; Hickson">ian</assigned_to>
          <cc>ian</cc>
    
    <cc>mathias</cc>
    
    <cc>mike</cc>
          
          <qa_contact>contributor</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>113724</commentid>
    <comment_count>0</comment_count>
    <who name="Michael[tm] Smith">mike</who>
    <bug_when>2014-10-24 18:14:53 +0000</bug_when>
    <thetext>In https://html.spec.whatwg.org/multipage/embedded-content.html#best-practices-for-metadata-text-tracks the data URL for the document provide in the iframe src attribute there there does not conform to the requirements in the URL spec.

The URL appears like this:

&lt;iframe src=&quot;data:text/html;charset=utf-8,&lt;!DOCTYPE%20html&gt;%0A&lt;style&gt;%0A%20body%2C%20html%20%7B%20ma…&lt;span&gt;Qual%20Match%2037&lt;%2Fspan&gt;%20&lt;span&gt;Friday%2014%3A21&lt;%2Fspan&gt;%0A&lt;%2Fdiv&gt;&quot; width=600 height=400&gt;&lt;/iframe&gt;

...but the characters &quot;&lt;&quot; and &quot;&gt;&quot; are not &quot;URL code points&quot; as defined in the URL spec, so they should instead be percent-encoded in that src value.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>113741</commentid>
    <comment_count>1</comment_count>
    <who name="Ian &apos;Hixie&apos; Hickson">ian</who>
    <bug_when>2014-10-24 22:45:57 +0000</bug_when>
    <thetext>It&apos;s tempting to suggest to Anne that we just allow &lt; and &gt; in URLs, thought I imagine people who want to write &lt;URL:http://foo&gt; wouldn&apos;t like that...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>113749</commentid>
    <comment_count>2</comment_count>
    <who name="Michael[tm] Smith">mike</who>
    <bug_when>2014-10-25 01:48:47 +0000</bug_when>
    <thetext>(In reply to Ian &apos;Hixie&apos; Hickson from comment #1)
&gt; It&apos;s tempting to suggest to Anne that we just allow &lt; and &gt; in URLs, thought
&gt; I imagine people who want to write &lt;URL:http://foo&gt; wouldn&apos;t like that...

Anne says, &quot;we could have a distinct conformance class for URLs in HTML attribute values but I don&apos;t really want to get into that before we actually have conforming URL parsers&quot;

(By the way, I notice The data: URI kitchen also doesn&apos;t percent-encode &lt; and &gt; in its output.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>113802</commentid>
    <comment_count>3</comment_count>
    <who name="Ian &apos;Hixie&apos; Hickson">ian</who>
    <bug_when>2014-10-27 20:38:24 +0000</bug_when>
    <thetext>Yeah that&apos;s why they didn&apos;t get encoded here, that&apos;s what I used. :-)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>115572</commentid>
    <comment_count>4</comment_count>
    <who name="Ian &apos;Hixie&apos; Hickson">ian</who>
    <bug_when>2014-11-26 22:46:20 +0000</bug_when>
    <thetext>Turns out the data: URL kitchen uses URI::Escape, and it does crazy eval() stuff when you try to pass it a pattern, which doesn&apos;t seem to work right, so I&apos;m not fixing the kitchen...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>115573</commentid>
    <comment_count>5</comment_count>
    <who name="">contributor</who>
    <bug_when>2014-11-26 22:46:35 +0000</bug_when>
    <thetext>Checked in as WHATWG revision r8862.
Check-in comment: escape more characters in example data: url (text track section)
https://html5.org/tools/web-apps-tracker?from=8861&amp;to=8862</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>