corysanin/tubestation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bug 1798388 - add Accessibility profiler category; convert existing code. r=canaltinova,eeejay

Browse Source 
We use profiler categories to separate out the profiler markers for major
components, such as DOM or Layout, to quickly understand what is happening in
each of them: this will also be helpful for accessibility. One might be
concerned that we're adding too many categories but I think it's fine: the
accessibility category shouldn't appear if accessibility services aren't in use.
Furthermore, if accessibility code is running when it's unexpected, having the
accessibility category appear will only highlight that fact.

Differential Revision: https://phabricator.services.mozilla.com/D160846
This commit is contained in:
Michael Comella
2022-11-02 16:23:24 +00:00
parent e4b2f7ed7f
commit 6b241593ea
3 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
accessible/base/NotificationController.cpp
View File

@@ -613,7 +613,7 @@ void NotificationController::ProcessMutationEvents() {
void NotificationController::WillRefresh(mozilla::TimeStamp aTime) {
Telemetry::AutoTimer<Telemetry::A11Y_TREE_UPDATE_TIMING_MS> timer;
AUTO_PROFILER_LABEL("NotificationController::WillRefresh", OTHER);
AUTO_PROFILER_LABEL("NotificationController::WillRefresh", A11Y);
// If the document accessible that notification collector was created for is
// now shut down, don't process notifications anymore.