Re: Fragment Identifiers for HTML5

Thanks. I'll fork my issue to a new thread.

On 6/22/08, Robert J Burns <rob@robburns.com> wrote:
> 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="&#8730; next">bottom</div>
>         <p><a href="#%E2%88%9A%20next">Go to bottom</a></p>
>         <p><a href="#&#8730; 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>


-- 
Michael

Received on Sunday, 22 June 2008 13:28:29 UTC