mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-08 02:14:43 +00:00
5e1a54c589
Previously, we cached when a UIA client was blocked or when there were no UIA clients. However, we did not cache the result when a UIA client was present but *not* blocked. This isn't normally a problem because a11y is normally instantiated in this case, which means we won't try to do any client detection again this session. However, if a11y is force disabled via the pref, we still do detection, but we don't instantiate. This meant that a UIA client which hammered us with queries would keep triggering the detection code, since we weren't caching the result. That resulted in severe performance degradation for impacted users. To fix this, cache the UIA detection result even if we do allow a11y instantiation. Differential Revision: https://phabricator.services.mozilla.com/D187869 |
||
|---|---|---|
| .. | ||
| ia2 | ||
| msaa | ||
| sdn | ||
| uia | ||
| moz.build | ||