- From: Michael A. Puls II <shadow2531@gmail.com>
- Date: Wed, 18 Feb 2009 03:24:33 -0500
- To: "Ian Hickson" <ian@hixie.ch>
- Cc: "Boris Zbarsky" <bzbarsky@mit.edu>, "HTML WG" <public-html@w3.org>
On Wed, 18 Feb 2009 03:03:18 -0500, Ian Hickson <ian@hixie.ch> wrote:
> On Wed, 18 Feb 2009, Michael A. Puls II wrote:
>> If so, implementing that in JS for clicking links (need something for
>> address field too) seems like you'd have to use .href and parse for the
>> fragid hvalue and decode for @id matching and getAttribute("href") and
>> parse for the fragid for @name matching. (assuming getAttribute("href")
>> in the browser returns the href as authored)
>
> I'm not sure what you mean here.
Just thinking out loud about the need for having the fragid available in its unencoded, unnormalized state for @name matching. Was just explaining that in JS terms. Nevermind.
> Are you proposing a particular change to
> what the spec says?
No. Just wanted to make sure I understood it. I see now.
--
Michael
Received on Wednesday, 18 February 2009 08:25:09 UTC