Page MenuHomePhabricator

Bug 2013141 - Make engines=all be the default. r=#style,oriol
ClosedPublic

Authored by emilio on Jan 29 2026, 8:08 AM.
Referenced Files
Unknown Object (File)
Thu, Apr 9, 7:58 PM
Unknown Object (File)
Thu, Apr 9, 5:33 PM
Unknown Object (File)
Thu, Apr 9, 2:25 AM
Unknown Object (File)
Tue, Apr 7, 10:03 PM
Unknown Object (File)
Sat, Apr 4, 1:49 PM
Unknown Object (File)
Fri, Apr 3, 12:33 AM
Unknown Object (File)
Thu, Mar 26, 12:18 PM
Unknown Object (File)
Thu, Mar 26, 11:33 AM
Subscribers

Details

Summary

I think at this point it is reasonable.

Diff Detail

Event Timeline

phab-bot changed the visibility from "Custom Policy" to "Public (No Login Required)".
phab-bot changed the edit policy from "Custom Policy" to "Restricted Project (Project)".
phab-bot removed a project: secure-revision.

My concern is that, when implementing a new property in Gecko, somebody will copy paste from an existing property that is supported in Servo, and will forget to add engines = "gecko". So the new property will also get enabled in Servo.

My concern is that, when implementing a new property in Gecko, somebody will copy paste from an existing property that is supported in Servo, and will forget to add engines = "gecko". So the new property will also get enabled in Servo.

Though I guess I can add an internal test in Servo that lists all webexposed properties. So that if people forget engines = "gecko", I will detect it when syncing.

This revision is now accepted and ready to land.Jan 29 2026, 5:42 PM

This revision requires a Testing Policy Project Tag to be set before landing. Please apply one of testing-approved, testing-exception-unchanged, testing-exception-ui, testing-exception-elsewhere, testing-exception-other. Tip: this Firefox add-on makes it easy!

Yeah we do have tests to avoid exposing properties accidentally in Gecko (we test that all properties we expose are in our property database).