51–60 of 72 posts
Earlier quoted context omitted.
I see, that would explain the performance issues. Why is it set up like that?
My understanding is that WebRender doesn't support everything yet, so right now it's mostly about validating correctness.
Earlier quoted context omitted.
I have the flag in my about:config with build `56.0a1 (2017-07-25) (64-bit)` under Linux. You're SO two days ago! Update your Nightly :)
Hmm, I got it through `ppa:ubuntu-mozilla-daily/ppa` on Ubuntu, so this is generally a couple days behind? Did you download it manually?
In fact it's likely: Firefox nightlies on Linux have been shipping stylo (preffed off) for close to three weeks, so if a two-day-old Ubuntu build doesn't have it, chances are neither will a newer one until they change their build configuration to use --enable-stylo.
I really like this idea of switching over to servo bit by bit. It makes me happy that there might be a real WebKit alternative again.
Servo's WebRender is also in the Firefox tree. I've seen some crazy benchmarks using it. It's not ready to be enabled widely yet, though.
I really like this idea of switching over to servo bit by bit. It makes me happy that there might be a real WebKit alternative again.
I'm new to frontend in general and wondering if I could trouble you for some context. Why is Firefox's CSS styling engine not already "in" the browser? To me it seems like Stylo is just a parallelized replacement for the old system, Servo. What am I missing here? Also, why are you celebrating an alternative for WebKit? Isn't it already supported by most major browsers?
Stylo takes Servo's styling engine and puts it inside Gecko.
Very cool. What parts of Servo are already in Firefox? What is missing? Is there a list of what will get into Firefox over time?
- Stylo, built by default, off by default
- Webrender, built by default, off by default, current pref makes it render things through both engines.
- rust-url for url parsing, built by default, off by default, current pref makes it parse through both parsers and compare. I intend to bring this across the finish line once done with stylo
- encoding_rs for dealing with string encodings. built and on by default. Not exactly a servo component (servo used to use rust-encoding), but i think servo uses it now.
Earlier quoted context omitted.
My understanding is that WebRender doesn't support everything yet, so right now it's mostly about validating correctness.
So it renders it two times and compares the results?
The proposed flag in about:config exists in Firefox Developer Edition too. I tried to enable it, then loaded some pages. There seems to be no distinction in visuals. Did it work seamlessly or is it currently NOP?
It won't be for dev edition; dev edition didn't build it by default.
about:config isn't user-facing so it will show prefs that do nothing on the current release channel or build.
Earlier quoted context omitted.
I'd argue that Gecko is a real WebKit alternative. It has improved quite dramatically lately, have you tried Firefox Nightly?
The problem with in its current state as a WebKit alternative is that it lacks stable api. We don't see any gecko based apps like we see WebKit based apps (electron, etc) because gecko is so tightly developed around Firefox.
If I want to use a web version I can do it using a browser of my choosing not the one developers want.
Earlier quoted context omitted.
Right. Servo is an engine that will be embeddable into apps that need to render HTML, not just browsers.
Ah, so like the omni-present webkit view?
Earlier quoted context omitted.
I have the flag in my about:config with build `56.0a1 (2017-07-25) (64-bit)` under Linux. You're SO two days ago! Update your Nightly :)
Hmm, I got it through `ppa:ubuntu-mozilla-daily/ppa` on Ubuntu, so this is generally a couple days behind? Did you download it manually?