• What Are Mozilla Service Workers
• Rust Web Browser

Mozilla #servo 31 Jan 2020. Servo/servo #25656 turned out a lot more. Servo had two major roles within Mozilla - as an incubator for novel browser technology we wanted to ship in Firefox, and more recently, as a lighter-weight vehicle for Mixed Reality products. The latter has been the focus for the last three years, and those products now appear to be winding down. Mozilla so far has refrained from making concrete plans for Servo - or Rust - to formally succeed Firefox or its use of C/C. For the time being, at least, Firefox remains Mozilla's browser of.

Stylo (a.k.a. QuantumCSS) will integrate Servo's CSS style system into Gecko, such that the style system code can be shared by Gecko and Servo. Stylo V1 will support Firefox on Windows, macOS, and Linux. Android support may ship in a later release. Stylo is a core part of Project Quantum.

To help test Stylo, download Firefox Nightly. Kaiba corp ygopro for mac. To confirm that Stylo is enabled, check about:support for 'Stylo: true (enabled by default)'. If it's not, then set the about:config pref layout.css.servo.enabled to true.

For a deep dive into Stylo internals, check out Lin Clark's Mozilla Hacks blog post 'Inside a super fast CSS engine: Quantum CSS (aka Stylo)'.

• 1Getting Involved
• 3Milestones
• 4Bugs

If you're interested in contributing to Stylo or Servo, drop by the #servo IRC channel on Mozilla's IRC server.

Sap serial number status esto. One front where you can help out is adding new properties to Servo's CSS parsing crate. This requires familiarity with Rust, but is otherwise a good way to dip your toes into Servo's style system. To get started, see Servo's CSS property hacking guide for more information.

If you do not know Rust, you can help implement keyword properties. See the Stylo hacking guide for more details. The Stylo hacking guide also has instructions for building Stylo if you wish to play with it yourself. If you know C++, Firefox bug 1277133 has information about easy Gecko bugs that will assist Stylo's integration with Gecko.

Some Stylo bugs that are good for new Servo contributors are tagged on GitHub as “easy” bugs and “less-easy” bugs.

Committing stylo changes

The process for committing a Stylo change that involves both Gecko and Servo changes is as follows:

1. Create a Github PR against https://github.com/servo/servo with the Servo changes in question.
2. Get that reviewed and checked into Servo's github repository.
3. Wait for servo-vcs-sync to land the Servo changes on Gecko's autoland.
4. Land the Gecko changes on autoland.

A more exhaustive / overwhelming description of the workflow is also available.

Try Syntax

For most Stylo changes, it should be sufficient to build on all platforms and test on Linux 64-bit only, which helps save resources in automation. To do this, you can use:

What Are Mozilla Service Workers

To build and test all Stylo platforms running in automation, you can use:

To build all possible platforms to ensure code compiles everywhere, but only test with Stylo enabled, you can use:

Stylo should not cause us to regress any CSS feature unless we explicitly decide that regressing that specific feature is acceptable. The existing test suite will be the primary benchmark of this, with cross-validation from an automated analysis and manual QA of the Alexa Top 500 sites.

• Stylo should be enabled by default on all desktop platforms.
• Stylo should have zero P1 and P2 bugs.
• Stylo should pass all (non-disabled) Gecko reftests and mochitests.
• Stylo should support at least as many CSS properties as than Gecko. Firefox = 375. Stylo = 375. Chrome = 276. DONE!
• Stylo should pass visual diff testing for the Alexa top sites. (bug 1331552) DONE!
• Stylo's sequential mode performance on Talos tp5 and tp6 should be at least as fast as Gecko's.
• Stylo's parallel mode performance on Talos tp5 and tp6 should be faster than Gecko's. Ideally, Stylo should scale linearly with the number of cores.
• Stylo's performance on Speedometer should be at least as fast as Gecko's.
• Stylo's memory usage (as measured by AWSY and user telemetry) should not exceed to Gecko's by more than X% (TBD).
• Stylo's crash rate should be less than or equal to Gecko's.
• Stylo's user engagement metrics should be greater than or equal to Gecko's.

stylo-central

• Run linux64-stylo tests in mozilla-central (bug 1330414) (dependencies)
  • Enable stop-gap vcs sync (bug 1317525)
  • Vendor servo in mozilla-central (bug 1322769)
  • Make all tests green (by skipping or expecting failure)

stylo-nightly

• Enable Stylo in Nightly (bug 1330412) (dependencies)
  • Implement parsing of all CSS properties supported by Firefox
  • Fix and enable all tests (without skipping or expecting failure)
  • Fix all crashes and assertion failures
    • Fuzz Stylo
    • Pass [Auto-tools/Projects/BugHunter Bughunter]
  • Manual QA sign-off
    • Smoke test Alexa Top N sites
    • Exploratory testing of browser UI and features

stylo-release

• Stylo meta bug 1243581 (dependencies)
• Run experiment comparing Stylo vs Gecko on engagement ratio, performance, crash rate, and memory usage.
• Let Stylo ride the trains
  • Enable Stylo on all platforms (bug stylo-nightly)
    • Pass QA on all platforms (tests, fuzzing, BugHunter)
• Ship Stylo to Release

P1 Bugs

No results.

0 Total;0 Open (0%);0 Resolved (0%);0 Verified (0%);

[stylo:p1] bugs:

No results.

0 Total;0 Open (0%);0 Resolved (0%);0 Verified (0%);

P2 Bugs

10 Total;10 Open (100%);0 Resolved (0%);0 Verified (0%);

[stylo:p2] bugs:

No results.

0 Total;0 Open (0%);0 Resolved (0%);0 Verified (0%);

P3 Bugs

50 Total;50 Open (100%);0 Resolved (0%);0 Verified (0%);

[stylo:p3] bugs:

No results.

0 Total;0 Open (0%);0 Resolved (0%);0 Verified (0%);

Bugzilla Queries

• Stylo milestone bug trees:
  • Build Stylo in Nightly (but pref'd off)

• Unprioritized 'stylo' whiteboard bugs to be triaged (Chris's list)

• Crash queries:

• Skipped or asserting tests: (these do not necessarily indicate Stylo bugs!)

Rust Web Browser

Priority Definitions:

• P1: Blocks shipping, more urgent. We should be working on these now/ASAP.
• P2: Blocks shipping, less urgent. We can wait a few weeks to start working on these.
• P3: Might block shipping. Needs re-evaluation, potentially closer to the deadline.
• P4: Doesn't block shipping, but nice to have.
• P5: Don't need to track.