- From: Robert J Burns <rob@robburns.com>
- Date: Sun, 22 Jun 2008 11:05:50 +0300
- To: Michael A.Puls II <shadow2531@gmail.com>
- Cc: Julian Reschke <julian.reschke@gmx.de>, HTML Issue Tracking WG <public-html@w3.org>
- Message-Id: <6D7A8E4B-3707-491E-A7C5-873D5B2414D9@robburns.com>
Hi Michael,
On Jun 21, 2008, at 6:21 PM, Michael A. Puls II wrote:
>
> Ah, that reminds me. I was also wondering if this fragid situation is
> covered anywhere in HTML5:
>
> <!DOCTYPE html>
> <html>
> <head>
> <meta charset="utf-8">
> <title></title>
> <style>
> div {
> position: absolute;
> top: 1000px;
> }
> </style>
> <script>
> //window.onload = function() {
> //alert(document.links[0].href);
> //alert(document.links[1].href);
> //};
> </script>
> </head>
> <body>
> <div id="√ next">bottom</div>
> <p><a href="#%E2%88%9A%20next">Go to bottom</a></p>
> <p><a href="#√ next">Go to the bottom 2</a></p>
> </body>
> </html>
>
> In both FF and Safari, clicking both the Go to bottom and Go to bottom
> 2 links take you to the bottom div. In Opera and IE neither one
> works.
>
> What's the correct behavior here?
It is hard to say what the correct behavior is since the id value is a
document conformance error (for HTML4.01 and XML 1) so the correct
behavior would be regarding error recovery which I don't think anyone
has specified. Part of what Erik’s bug submission[1] seeks to address
relates both to what authors specify for IDREFs and how UAs handle
pointers to document fragments (including pointers involving IDREFs).
Obviously it would make sense for the HTML WG to address these issues,
but for some reason this is a taboo topic and the bug has to be closed
immediately without proper resolution.
Take care,
Rob
[1]: <http://www.w3.org/Bugs/Public/show_bug.cgi?id=5744>
Received on Sunday, 22 June 2008 08:06:44 UTC