1859538 - Allow chrome stylesheets to be parsed in parallel.

Status: RESOLVED FIXED

(Core :: CSS Parsing and Computation, enhancement)

Comment 1

[Emilio Cobos Álvarez (:emilio)]

Attachment: Bug 1859538 - Allow chrome stylesheets to be parsed in parallel. r=#layout!,#theme!

This changes -moz-bool-pref from @supports to @media, bringing various
improvements:

• @media (-moz-bool-pref) properly reacts to dynamic changes.
• We no longer need to parse chrome:// stylesheets in the main thread
  (-moz-bool-pref was the only thing that forced us to do that).

This makes privileged and non-privileged stylesheets more similar.

Comment 2

[samcarey909]

With the increasing complexity of web applications, the loading and rendering speed of a webpage can significantly impact user experience. Incorporating parallel parsing of stylesheets in Chrome can drastically enhance the loading efficiency of websites. However, delving deeper into this topic requires extensive research and a thorough grasp of web development concepts. For individuals facing challenges in comprehending this subject, seeking expert guidance through assignment help can provide invaluable insights and assist in navigating the complexities of optimizing browser performance.
assignment help

Comment 3

[samcarey909]

With the increasing complexity of web applications, the loading and rendering speed of a webpage can significantly impact user experience. Incorporating parallel parsing of stylesheets in Chrome can drastically enhance the loading efficiency of websites. However, delving deeper into this topic requires extensive research and a thorough grasp of web development concepts. For individuals facing challenges in comprehending this subject, seeking expert guidance through assignment help can provide invaluable insights and assist in navigating the complexities of optimizing browser performance.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0f84d30b2de4
Allow chrome stylesheets to be parsed in parallel. r=layout-reviewers,desktop-theme-reviewers,dao,Gijs,tlouw

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/3792590da739
Fix parsing of -moz-bool-pref.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/fe39bff2df5e
Fix browser_tab_manager_drag.js.

Comment 7

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/0f84d30b2de4
https://hg.mozilla.org/mozilla-central/rev/3792590da739
https://hg.mozilla.org/mozilla-central/rev/fe39bff2df5e

Comment 8

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

There is still the moz_gtk_csd_rounded_bottom_corners atom which seems to be unused now. Are there plans to sync widget.gtk.rounded-bottom-corners.enabled or should it be removed?

Comment 9

[Emilio Cobos Álvarez (:emilio)]

Not sure what "sync" means in that context, but it can be removed.

Comment 10

[Andrej (:aglavic)]

(In reply to Norisz Fay [:noriszfay] from comment #7)

https://hg.mozilla.org/mozilla-central/rev/0f84d30b2de4
https://hg.mozilla.org/mozilla-central/rev/3792590da739
https://hg.mozilla.org/mozilla-central/rev/fe39bff2df5e

== Change summary for alert #40019 (as of Mon, 23 Oct 2023 06:58:10 GMT) ==

Improvements:

Ratio	Test	Platform	Options	Absolute values (old vs new)
3%	ts_paint	windows10-64-shippable-qr	e10s fission stylo webrender	440.92 -> 429.08
2%	sessionrestore	windows10-64-shippable-qr	e10s fission stylo webrender	490.08 -> 479.25
2%	startup_about_home_paint	windows10-64-shippable-qr	e10s fission stylo webrender	653.04 -> 639.42
2%	sessionrestore_no_auto_restore	windows10-64-shippable-qr	e10s fission stylo webrender	503.96 -> 493.67

For up to date results, see: https://treeherder.mozilla.org/perfherder/alerts?id=40019