Closed
Bug 607538
Opened 14 years ago
Closed 14 years ago
remove support of accessibility.disablecache preference
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
mozilla2.0b8
People
(Reporter: surkov, Assigned: surkov)
References
()
Details
(Keywords: access, dev-doc-complete)
Attachments
(1 file, 1 obsolete file)
2.73 KB,
patch
|
MarcoZ
:
review+
benjamin
:
approval2.0+
|
Details | Diff | Splinter Review |
It's not honored any more (we cache accessibles, get them from cache, the only affect it has we always invalidate children when AT asks for children, that's not disabled cache really) and not used I think. http://kb.mozillazine.org/Accessibility.disablecache says is mostly for debugging propose.
Attachment #486258 -
Flags: review?(marco.zehe)
Attachment #486258 -
Flags: approval2.0?
Assignee | ||
Comment 1•14 years ago
|
||
previous patch was wrong
Assignee: nobody → surkov.alexander
Attachment #486258 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #486262 -
Flags: review?(marco.zehe)
Attachment #486262 -
Flags: approval2.0?
Attachment #486258 -
Flags: review?(marco.zehe)
Attachment #486258 -
Flags: approval2.0?
Comment 2•14 years ago
|
||
Comment on attachment 486262 [details] [diff] [review] patch2 r=me. But is there some JS file that also has this pref defined where we need to remove it? E. G. this once showed up in about:config, right? So ti must be defined in some prefs.js file or the like. Please check before landing and remove it there, too.
Attachment #486262 -
Flags: review?(marco.zehe) → review+
Assignee | ||
Comment 3•14 years ago
|
||
It isn't referred anywhere outside of a11y, it isn't presented in about:config.
Comment 4•14 years ago
|
||
All right, thanks for checking! So this is completely useless code now. :) Yeah, let's ditch it! Thanks for finding!
Updated•14 years ago
|
Attachment #486262 -
Flags: approval2.0? → approval2.0+
Assignee | ||
Comment 5•14 years ago
|
||
Benjamin, am I allowed to land it while tree is restricted to Gecko 2 beta 7 blockers?
Comment 6•14 years ago
|
||
No.
Assignee | ||
Comment 7•14 years ago
|
||
landed on 2.0 - http://hg.mozilla.org/mozilla-central/rev/7f42cc721784
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b8
Assignee | ||
Updated•14 years ago
|
Keywords: dev-doc-needed
Comment 8•14 years ago
|
||
This isn't already documented anywhere on MDC, but I added a note to Fx4 for developers: https://developer.mozilla.org/en/Firefox_4_for_developers#Other_changes
Keywords: dev-doc-needed → dev-doc-complete
Assignee | ||
Comment 9•14 years ago
|
||
Yes, thank you. Perhaps it makes sense to update article on http://kb.mozillazine.org. I just don't know who is responsible for it.
You need to log in
before you can comment on or make changes to this bug.
Description
•