Closed
Bug 1765964
Opened 3 years ago
Closed 3 years ago
[CTW] Don't send scroll position if it's 0
Categories
(Core :: Disability Access APIs, task)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
101 Branch
Tracking | Status | |
---|---|---|
firefox101 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
Details
Attachments
(1 file)
BundleFieldsForCache sends a value for scrollPosition even if the frame is not scrollable or it's at position 0 (not scrolled). As a memory optimisation (particularly given that most nodes aren't scrollable), we should assume the nonexistence of the property means the default of 0.
RemoteAccessibleBase is already handling this correctly. We just need to change BundleFieldsForCache to only include if non-0, and include DeleteEntry otherwise (for cache updates).
Assignee | ||
Comment 1•3 years ago
|
||
In addition, don't send DeleteEntry for Transform for an initial cache update, since there's nothing to delete.
These fixes don't change the behaviour for users, but optimise both cache storage and IPC trafic.
Updated•3 years ago
|
Assignee: nobody → jteh
Status: NEW → ASSIGNED
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/206e9f1849c2
Don't push scrollPosition to the cache if it's 0. r=morgan
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox101:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•