Closed
Bug 406154
Opened 17 years ago
Closed 17 years ago
document accessible nodes all vanish after navigation
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: steve, Assigned: aaronlev)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b2pre) Gecko/2007112904 Minefield/3.0b2pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b2pre) Gecko/2007112904 Minefield/3.0b2pre
The document nodes all disappear after navigating to another page and then back.
click the 'Namespace Members' link at the top and then use toolbar back button.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Sorry I confirmed the bug too quickly:
Then browse down to the 'document frame' in accerciser.
It is not there but an invalid role and a red cross icon appear.
Does doing a refresh in accerciser or restarting accerciser work for you?
Hi Ginn, no I spent ages on this to get a good repro as it kept happening in od circumstances. This way is 100% reproducible. If you do the above with accerciser closed and than run it you see the problem.
I found in some case closing/opening nodes or refresh they seemed to be around but closing/opening accerciser causes the problem to show. Almost as if accersiser is caching the dead nodes or perhaps keeping them live. In fact I've not seen that 'invalid' before, just <dead> for nodes that have gone.
Assignee | ||
Comment 4•17 years ago
|
||
Marco, can you take a look?
Comment 5•17 years ago
|
||
Steve, can you still reproduce it with the current nightly build? I do not see the problem. But I am running Orca, which may influence the results.
hey I was just trying it ;-)
No whatever I do it doesn't happen now.
It's probably nothing to do with it but on that day I also found that the div holding the top links did not resize with horiz. resize, but it does now.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Comment 7•17 years ago
|
||
Thanks for looking into it, Steve! One bug less on our agenda...
You need to log in
before you can comment on or make changes to this bug.
Description
•