Closed
Bug 174796
Opened 23 years ago
Closed 23 years ago
XUL browser's MSAA cache not working correctly
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
Attachments
(1 file)
|
6.53 KB,
patch
|
mozilla
:
review+
bryner
:
superreview+
roc
:
approval+
|
Details | Diff | Splinter Review |
I have experienced a number of problems with the IEnumVARIANT MSAA Cache checked
in this summer.
- Incorrect or repeated nodes
- cache not getting reset for new documents
- no way to test with cache turned off, to see where problem lies
| Assignee | ||
Comment 1•23 years ago
|
||
These are the 2 new user prefs for controlling the cache:
user_pref("accessibility.disablecache", true/false);
user_pref("accessibility.disableenumvariant", true/false);
| Assignee | ||
Comment 2•23 years ago
|
||
Seeking r=jgaunt
| Assignee | ||
Comment 3•23 years ago
|
||
*** Bug 174949 has been marked as a duplicate of this bug. ***
Comment 4•23 years ago
|
||
Comment on attachment 103069 [details] [diff] [review]
Fixes IEnumVARIANT::Next() loop, implements hidden cache prefs, clears cache when new doc is loaded
r=jgaunt
Attachment #103069 -
Flags: review+
Comment 5•23 years ago
|
||
Comment on attachment 103069 [details] [diff] [review]
Fixes IEnumVARIANT::Next() loop, implements hidden cache prefs, clears cache when new doc is loaded
sr=bryner
Attachment #103069 -
Flags: superreview+
Comment on attachment 103069 [details] [diff] [review]
Fixes IEnumVARIANT::Next() loop, implements hidden cache prefs, clears cache when new doc is loaded
a=roc+moz for trunk
Attachment #103069 -
Flags: approval+
Comment 7•23 years ago
|
||
This has approval. If it doesn't get checked in by the early morning tree
closure on Nov 5, 2002 it's going to have to wait until after the branch is cut.
| Assignee | ||
Comment 8•23 years ago
|
||
Fixed
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 9•23 years ago
|
||
Was this checked in before the 1.2 branch was cut? Or was it checked in onto
the branch?
| Assignee | ||
Comment 10•23 years ago
|
||
checked in before the cut. (I thought the cut occured on the 5th?!).
You need to log in
before you can comment on or make changes to this bug.
Description
•