Closed
Bug 310377
Opened 19 years ago
Closed 19 years ago
Only one open tab QI's for ISimpleDOMText
Categories
(Firefox :: Disability Access, defect)
Tracking
()
VERIFIED
FIXED
Firefox1.5
People
(Reporter: tim.mchyde, Assigned: aaronlev)
References
()
Details
(Keywords: access, fixed1.8)
Attachments
(1 file)
973 bytes,
patch
|
mkaply
:
review+
bryner
:
superreview+
mtschrep
:
approval1.8b5+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050927 Firefox/1.6a1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050927 Firefox/1.6a1 Whenever you switch tabs, the accessible object returned by AccessibleObjectFromPoint should be able to QI for ISimpleDOMText. However this only works for at most one open tab (which tab this is changes as you open and clsoe tabs and navigate inside a tab according to a logic I cannot determine). Also this is a problem sometimes with just one tab if you click a link and go back but in this case it does not consistently fail but seems to most of the time, especially if you go from a file clicked from teh desktop to open Deer park and then click a link in that file to a website. Reproducible: Always Steps to Reproduce: 1. Open Deer Park to any page, default alpha 2 page is fine 2. use my tester app from the above URL to see that the ISimpleDOMText is giving data wherever the mouse is 3. ctrl+click any link to open a new tab Actual Results: Notice that either the new tab does not work with the tester or the original tab stops working 4. Now try closing the tab that works and notice the other tab that didnt work, now works! Expected Results: all tabs should work with ISimpleDOMText regardless of what order they were opened or what tabs were shut. All the tester app is doing is to QI's ISimpleDOMText from the accessible object for the present tab. It works inconsistently with multiple tabs or in the same tab across multiple pages in history.
Reporter | ||
Comment 1•19 years ago
|
||
Correction: Closing a tab does not seem to ever make another tab work. But going Back in history to the original page of a tab sometimes makes that tab start working. Further data: ISimpleDOMNode seems to be always be present (QI's from IAccessible) even when ISimpleDOMText doesnt
Assignee | ||
Updated•19 years ago
|
Assignee | ||
Updated•19 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → aaronleventhal
Status: ASSIGNED → NEW
Assignee | ||
Updated•19 years ago
|
Target Milestone: --- → Firefox1.5
Assignee | ||
Comment 2•19 years ago
|
||
Attachment #198315 -
Flags: review?(timeless)
Assignee | ||
Updated•19 years ago
|
Attachment #198315 -
Flags: review?(timeless) → review?(parente)
Assignee | ||
Updated•19 years ago
|
Attachment #198315 -
Flags: superreview?(jst)
Comment 3•19 years ago
|
||
Comment on attachment 198315 [details] [diff] [review] When a new document has finished loading, make the outer doc accessible forget about the old doc accessible chilld r=mkaply
Attachment #198315 -
Flags: review?(parente) → review+
Assignee | ||
Updated•19 years ago
|
Flags: blocking1.8b5?
Whiteboard: [ETA: need sr= and approval. This breaks magnifcation apps ]
Assignee | ||
Updated•19 years ago
|
Attachment #198315 -
Flags: superreview?(jst) → superreview?(jag)
Updated•19 years ago
|
Attachment #198315 -
Flags: superreview?(jag) → superreview+
Assignee | ||
Updated•19 years ago
|
Attachment #198315 -
Flags: approval1.8b5?
Updated•19 years ago
|
Attachment #198315 -
Flags: approval1.8b5? → approval1.8b5+
Assignee | ||
Updated•19 years ago
|
Flags: blocking1.8b5?
Whiteboard: [ETA: need sr= and approval. This breaks magnifcation apps ] → ]
Assignee | ||
Comment 4•19 years ago
|
||
This only fixed AccessibleObjectFromPoint for history, not for 2nd tabs. We need to deal with the tabbed browsing issue.
Keywords: fixed1.8
Whiteboard: ]
Assignee | ||
Comment 5•19 years ago
|
||
Tim, may be you can verify this timeframe: 9/14 - broken 9/15 - fixed
Assignee | ||
Comment 6•19 years ago
|
||
(In reply to comment #5) > 9/14 - broken > 9/15 - fixed Scratch that.
Assignee | ||
Comment 7•19 years ago
|
||
This was caused by bug 309329. A patch in bug 311460 fixes this.
Assignee | ||
Updated•19 years ago
|
Reporter | ||
Comment 8•19 years ago
|
||
My original test cases that failed now work. Verified fixed.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•