- From: Ashley Sheridan <ash@ashleysheridan.co.uk>
- Date: Tue, 14 May 2013 22:37:40 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>, Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net>
- Cc: WHATWG <whatwg@lists.whatwg.org>, Kyle Simpson <getify@gmail.com>
I thought the point was that the JavaScript event would fire before the scroll, which would allow you to cancel the default action, no? "Tab Atkins Jr." <jackalmage@gmail.com> wrote: >On Tue, May 14, 2013 at 2:31 PM, Nils Dagsson Moskopp ><nils@dieweltistgarnichtso.net> wrote: >> Kyle Simpson <getify@gmail.com> schrieb am Tue, 14 May 2013 16:08:17 >> -0500: >>> There have been times this automatic behavior has been quite >annoying >>> because of accidential ID/hash overlap. >> >> Please explain how a document subresource can be “accidentally” >> referred to by a URL be “accidental”. I do not understand it. > >You're using a hash to store information that is used by JS. You also >use ids on your page. These can collide unintentionally, causing a >scroll on page load. > >~TJ Thanks, Ash
Received on Tuesday, 14 May 2013 21:38:07 UTC