- From: Glenn Maynard <glenn@zewt.org>
- Date: Wed, 19 Dec 2012 08:09:59 -0600
- To: Philip Jägenstedt <philipj@opera.com>
- Cc: whatwg <whatwg@lists.whatwg.org>, Ian Hickson <ian@hixie.ch>, Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net>
On Wed, Dec 19, 2012 at 4:19 AM, Philip Jägenstedt <philipj@opera.com>wrote: > What should a browser do with a URL ending with #foo&t=10 if there is an > element on the page with id="foo&t=10"? What about #foo&bar if there is an > element with id="foo"? I would be surprised if treating #foo& the same as > #foo were Web compatible... > What if the page already uses this format for the hash, and is using the key "t" for something else? I shouldn't need to worry that my hash keys are suddenly going to gain second meanings. What if the page uses a different format for the hash? I use "#foo/bar?a=b&c=d" (giving me a path segment within the hash, which is extremely useful). What if the video element doesn't exist on page load, because it's created by dynamically by a script? You can't simply apply the time to every video, since the page might be going through a playlist and you surely don't want "t=30" to cause every song or video in the playlist to start at 30s. -- Glenn Maynard
Received on Wednesday, 19 December 2012 14:10:28 UTC