Skip to content
Permalink
Browse files

[e] (0) List some of the differences, to make Julian happier.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10804

git-svn-id: http://svn.whatwg.org/webapps@5565 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Sep 30, 2010
1 parent 099f1f2 commit e15fa224c7e854c896e4a2a08c9ed012f0a06388
Showing with 18 additions and 6 deletions.
  1. +6 −2 complete.html
  2. +6 −2 index
  3. +6 −2 source
</dl></li>

</ol><p class=note>This requirement is a <a href=#willful-violation>willful violation</a>
of the HTTP specification, motivated by the need for backwards
compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>
of the HTTP specification (for example, HTTP doesn't allow the use
of single quotes and requires supporting a backslash-escape
mechanism that is not supported by this algorithm<!-- not to mention
not having any rules for error-handling, which is of course why
we're having to define it ourselves -->), motivated by the need for
backwards compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>

</div>

8 index
</dl></li>

</ol><p class=note>This requirement is a <a href=#willful-violation>willful violation</a>
of the HTTP specification, motivated by the need for backwards
compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>
of the HTTP specification (for example, HTTP doesn't allow the use
of single quotes and requires supporting a backslash-escape
mechanism that is not supported by this algorithm<!-- not to mention
not having any rules for error-handling, which is of course why
we're having to define it ourselves -->), motivated by the need for
backwards compatibility with legacy content. <a href=#refsHTTP>[HTTP]</a></p>

</div>

8 source
@@ -6231,8 +6231,12 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
</ol>

<p class="note">This requirement is a <span>willful violation</span>
of the HTTP specification, motivated by the need for backwards
compatibility with legacy content. <a
of the HTTP specification (for example, HTTP doesn't allow the use
of single quotes and requires supporting a backslash-escape
mechanism that is not supported by this algorithm<!-- not to mention
not having any rules for error-handling, which is of course why
we're having to define it ourselves -->), motivated by the need for
backwards compatibility with legacy content. <a
href="#refsHTTP">[HTTP]</a></p>

</div>

0 comments on commit e15fa22

Please sign in to comment.
You can’t perform that action at this time.