W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2009

[whatwg] localStorage feedback

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 13 Oct 2009 15:20:56 +1300
Message-ID: <11e306600910121920u51f41692jf4673efe4e9e9b3c@mail.gmail.com>
On Tue, Oct 13, 2009 at 3:07 PM, Ian Hickson <ian at hixie.ch> wrote:

> On Wed, 9 Sep 2009, Darin Fisher wrote:
> > What about navigating an iframe to a reference fragment, which could
> > trigger a scroll event?  The scrolling has to be done synchronously for
> > compat with the web.
>
> You can only do that with same-domain pages, as far as I can tell.
>
> (Does that really have to be synchronous?


Later in the thread I mentioned that in Gecko, the 'scroll' event is
asynchronous, which suggests that Web compatibility does not require it to
be synchronous.


> Right now we don't define the
> 'scroll' event anywhere. What are the semantics it needs?)
>

Perhaps it should be defined in CSSOM, alongside scrollTop/scrollLeft?

In Gecko, it's just something that fires asynchronously after a node's
scrollTop/scrollLeft have changed. Scroll events for the viewport fire at
the document and bubble to the window, scroll events on elements with
'overflow' not 'visible' fire at that element and don't bubble.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091013/14dbd60d/attachment.htm>
Received on Monday, 12 October 2009 19:20:56 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:18 UTC