api: Flatten and simplify Servo preferences (#34966)

Flatten and simplify Servo's preferences code. In addition, have both
preferences and options passed in as arguments to `Servo::new()` and
make sure not to use the globally set preferences in `servoshell` (as
much as possible now).

Instead of a complex procedural macro to generate preferences, just
expose a very simple derive macro that adds string based getters and
setters.

- All command-line parsing is moved to servoshell.
- There is no longer the concept of a missing preference.
- Preferences no longer have to be part of the resources bundle because
  they now have reasonable default values.
- servoshell specific preferences are no longer part of the preferences
  exposed by the Servo API.

Signed-off-by: Martin Robinson <mrobinson@igalia.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/components/script/init.rs b/components/script/init.rs
index 324714a3831..f2e88f6ea1a 100644
--- a/components/script/init.rs
+++ b/components/script/init.rs
@@ -62,7 +62,7 @@ unsafe extern "C" fn is_dom_object(obj: *mut JSObject) -> bool {
 #[allow(unsafe_code)]
 pub fn init() -> JSEngineSetup {
     unsafe {
-        if pref!(js.disable_jit) {
+        if pref!(js_disable_jit) {
             js::jsapi::DisableJitBackend();
         }
         proxyhandler::init();