Ian explained to me on IRC that IE and Opera are consuming the entire
document as a comment and reparsing for (i.e., --! is not treated
specially). That is supported by the following test case:
http://crypto.stanford.edu/~abarth/research/html5/comments/bang-gt.html
Safari and Firefox contain
In http://www.whatwg.org/specs/web-apps/current-work/#resolving, the
spec says:
If the URL to be resolved was passed to an API
The base URL is the document base URL of the script's script
document context.
I believe browsers differ on this point. When resolving a URL
received from a script,
It looks like Mozilla is planning to change their behavior to match
the HTML5 spec in this regard. See the patch in
https://bugzilla.mozilla.org/show_bug.cgi?id=214476.
Adam
On Fri, Jun 27, 2008 at 1:52 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Jun 27, 2008, at 12:13 AM, Adam Barth
One focus area for HTML5 has been to solidify the concept of Web
pages as Web Applications and to introduce concepts to flesh out this
new Web Application concept such as the application name, more
flexible icons, offline data storage, and online/offline discovery.
There is one aspect to
On Mon, 17 Apr 2006, Henri Sivonen wrote:
In WA 1.0 and WF 2.0 some values are required to be IRIs and some values
are required to be IRI references. I'm confused about what exactly this
means in terms of conformance checking. (WF 2.0 does say something about
processing in a browser,
On Tue, 13 Mar 2007, L. David Baron wrote:
The wording of the value of href for base elements [1] is not quite the
same as the wording for anchor elements [2], and technically [3] that
wording allows only absolute URIs. They should probably both say they
allow URI references (or IRI
On Wed, 11 Apr 2007, Geoffrey Sneddon wrote:
Looking through the spec again, there is nothing about backslashes in
URI's path being treated as a forward slash, behaviour needed for
compatibility for quite a few websites.
On Wed, 11 Apr 2007, Gervase Markham wrote:
I would be rather
On 6/27/08, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 11 Apr 2007, Michael A. Puls II wrote:
However, we can't specify this for all URIs (just saying). Flipping raw
backslashes (even though they should really be encoded) in a
href=mailto:uridata; for example, should not be done.
