Don't send custom property declarations to getCSSDeclarationBlockIssues
Categories
(DevTools :: Inspector: Rules, task)
Tracking
(firefox132 verified, firefox133 verified)
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
Those are completely ignored on the server, so let's not send them in the first place to save some cycle
getCSSDeclarationBlockIssues(declarations, browsers) {
...
for (const { name: property } of declarations) {
// Ignore CSS custom properties as any name is valid.
if (property.startsWith("--")) {
continue;
}
Assignee | ||
Comment 1•2 months ago
|
||
Updated•2 months ago
|
Assignee | ||
Comment 2•2 months ago
|
||
Those declarations are already ignored on the server, as custom property
declaration can't have compatibility issues.
On pages with lots of CSS variables, we were still paying the price of
iterating over those and sending them through RDP, which could be costly.
Updated•2 months ago
|
Comment 4•2 months ago
|
||
bugherder |
Assignee | ||
Comment 5•2 months ago
|
||
Those declarations are already ignored on the server, as custom property
declaration can't have compatibility issues.
On pages with lots of CSS variables, we were still paying the price of
iterating over those and sending them through RDP, which could be costly.
Original Revision: https://phabricator.services.mozilla.com/D224472
Updated•2 months ago
|
Comment 6•2 months ago
|
||
beta Uplift Approval Request
- User impact if declined: DevTools Inspector completely freezes when inspecting a page using lots of CSS variables
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: Follow steps from https://bugzilla.mozilla.org/show_bug.cgi?id=1922469#c0
- Risk associated with taking this patch: low
- Explanation of risk level: simple DevTools only fix
- String changes made/needed: -
- Is Android affected?: no
Updated•2 months ago
|
Updated•2 months ago
|
Updated•1 months ago
|
Comment 8•1 months ago
•
|
||
I was able to reproduce the issue on an affected Firefox 132.0b3 build, using macOS 14.6, while following the steps from https://bugzilla.mozilla.org/show_bug.cgi?id=1922469#c0, as mentioned in Comment 6.
Verified as fixed using Firefox Nightly 133.0a1 (2024-10-06) and Firefox 132.0b4 (treeherder build from Comment 7), on macOS 14.6, Windows 11 and Ubuntu 22.04. The inspector is no longer freezing after pressing the "Open dialog" button from https://sanomalearning.design/categories/components/dialog/usage/.
Description
•