On May 30, 2013, at 11:34 AM, Boris Zbarsky wrote:
> On 5/30/13 2:26 PM, Brady Eidson wrote:
>>> So how does your setup differ in a way that actually makes this
>>> impossible to implement?
>>
>> The design is that after pagehide returns, if the traversal is still
>> taking place and the page i
Outlook i suspect (v. pipermail) removed one of my links to the original bug
posting at w3c: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22022.
For convenience, view my email with paragraph breaks at http://ow.ly/lyq8H-
Chris
From: follybeach...@hotmail.com
To: whatwg@lists.whatwg.org
Subject
On 5/30/13 2:26 PM, Brady Eidson wrote:
So how does your setup differ in a way that actually makes this
impossible to implement?
The design is that after pagehide returns, if the traversal is still
taking place and the page is going into the cache, no further events
take place.
Yes, you said
On 5/30/13 2:24 PM, Brady Eidson wrote:
In WebKit, if you have an unload handler, you don’t go into the page cache.
This is also true in Gecko; I was talking about the events we dispatch,
not necessarily what a page can see.
-Boris
in case the associated thread of messages for this subject are not referenced
by pipermail via this post's title, I wanted to link to them
here-http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-September/023084.html.
I'm writing to discuss/obtain clarification regarding a post that was int
On May 30, 2013, at 10:38 AM, Boris Zbarsky wrote:
> On 5/30/13 1:04 PM, Brady Eidson wrote:
>> The long standing design goals and implementation of our page cache
>> prevents us from delivering these events to a page that was just sent
>> “pagehide with persisted set to true”.
>
> Actually, le
On May 30, 2013, at 10:31 AM, Boris Zbarsky wrote:
> On 5/30/13 1:04 PM, Brady Eidson wrote:
>> Correct. Of course note that pages that have been placed in the page
>> cache that are evicted have no visibility that the eviction occurred (at
>> least in WebKit)
>
> I believe this is also true i
On 5/30/13 1:04 PM, Brady Eidson wrote:
The long standing design goals and implementation of our page cache
prevents us from delivering these events to a page that was just sent
“pagehide with persisted set to true”.
Actually, let me try to clarify this a bit.
The way I would imagine logic lik
On 5/30/13 1:04 PM, Brady Eidson wrote:
Correct. Of course note that pages that have been placed in the page
cache that are evicted have no visibility that the eviction occurred (at
least in WebKit)
I believe this is also true in Gecko.
Let me ask you this - Are there any (reasonable) pages
On 5/30/13 12:41 PM, Brady Eidson wrote:
pageshow is a history traversal event, and not a visibility event. I
don’t see a guarantee in any spec that “pageshow” comes after the
document is actually visible.
It comes after it's visible in terms of document.visibilityState, for
pages not in backg
On May 29, 2013, at 6:36 PM, Boris Zbarsky wrote:
> Let's actually back up a second.
>
> What problem are you really trying to solve by changing the ordering? As I
> see it, right now the situation is as follows (in implementations, if not in
> the spec):
>
> 1) pagehide fires, with a boole
On May 29, 2013, at 5:34 PM, Boris Zbarsky wrote:
> On 5/29/13 4:30 PM, Brady Eidson wrote:
>> I see in the HTML spec that the step *before* firing pagehide is “set
>> the Document’s page showing flag to false,” but I can’t find language
>> that says pagehide fires *before* the page is actually
On Wed, May 29, 2013 at 3:19 PM, Ian Hickson wrote:
> On Wed, 27 Feb 2013, Adam Klein wrote:
>>
>> Consider the following script:
>>
>> tr = document.createElement('tr')
>> tr.innerHTML = '';
>>
>> That is, the fragment is parsed with tr as the context element. What
>> should the generated DOM be?
Le 30 mai 2013 à 12:39, Michael[tm] Smith a écrit :
> Alex or somebody else writes up an alternative API proposal they can be
> happier with, it seems unlikely they're going to be re-implementing
> anything based on the current Microdata API spec.
In the process, if it ever happens, I would love
14 matches
Mail list logo
