I managed to reliably reproduce this in Marco's blog via scratchpad. Tried isolating it and making a mochitest, but no luck. Even saving the HTML and using it unmodified does not work. STR: 1. Enable chrome access in scratchpad. 2. Load attachment in scratchpad. 3. Go to http://www.marcozehe.de/ 4. Press ctrl+l in scratchpad and quickly switch to main window. 5. Look at dump() output.

> STR: > 1. Enable chrome access in scratchpad. how?

(In reply to alexander :surkov from comment #1) > > STR: > > 1. Enable chrome access in scratchpad. > > how? https://developer.mozilla.org/en/Tools/Scratchpad#Using_Scratchpad_to_access_Firefox_internals

Again, the original bug 758884 was a very recent regression, between the May 24, 2011 nightly build, where the test definitely still worked, and the May 26 build, where it did first show up. I tried to get at the May 25 build, but because of the weirdness of that HTC keyboard, gave up trying to enter the URL to the FTP server. Eitan, you should be able to narrow down the regression range to the checkins between those two dates.

1) you get a link accessible 2) it's destroyed (node is removed from doc cache) 3) its container is destroyed 3) new accessible for container (and thus for link) is created (node is added to doc cache) 4) IsInDocument() returns true for the node of destroyed link accessible (thus no stale state) 5) destroyed link accessible isn't defunct because of event coalesce problem I have one old wip on 5, hope to finish it one day. 4 is new for me.

filed bug 760354 for IsInDocument problem (4 item from comment #4).

bug 807911 should address 5th item.

Now I end up getting 1) "Not stale, the accessible is still in document cache" 2) "Defunct, so don't bother getting the parent" 1st was supposed to be fixed by bug 760354. It didn't happen due to some reason 2nd was fixed by bug 807911 and now we are in good shape. Marco, what's special about 'Skip link' on your blog so its accessible gets recreated whenever it's focused?

When it gets focused, its styling is changed so it is moved into the view port and its focus outline is shown. Before that, it's hidden. The example comes from the WordPress Accessible TwentyTen child theme by Sylvia Egger, http://accessible.sprungmarker.de/2011/01/accessible-1-0/

Marco, you know which style?

Not off-hand. I'd have to dig just like you. But there's only this one style for skip links IIRC.

(In reply to alexander :surkov from comment #7) > Now I end up getting > > 1) "Not stale, the accessible is still in document cache" > 2) "Defunct, so don't bother getting the parent" > > 1st was supposed to be fixed by bug 760354. It didn't happen due to some > reason > 2nd was fixed by bug 807911 and now we are in good shape. we don't calculate any state if accessible is defunct so 1st was really fixed by bug 807911. marking fixed by bug 760354 (Mozilla 16) and bug 807911 (Mozilla 19).