I run Firefox-nightly and rendering feels faster with layout.css.servo.enabled. Together with the multi process architecture this is really a big improvement :-) If I could run Firefox now on Wayland I would be happy (even if it doesn't work perfect, I know there are some test builds but that's nothing I would use).
Announcement
Collapse
No announcement yet.
Rust-Written "Stylo" Servo Style System Now Available Via Firefox Nightly
Collapse
X
-
For what it's worth, I've been using Firefox at home and Chrome for work for the last seven years. No matter what the benchmarks said, Chrome felt substantially faster. But in the last few months Firefox Nightly has finally started narrowing the gap.
It still seems to slow down after being open for a few days, which is a disappointment.
Comment
-
Originally posted by uid313 View PostUnfortunately Firefox does not yet support the <dialog> element.
May I ask what is it you can't do because FF doesn't enable that out of the box?
Comment
-
Originally posted by bug77 View Post
Nothing, but blink supports <dialog> atm. Firefox also has support, but you have to enable it: http://caniuse.com/#feat=dialog
May I ask what is it you can't do because FF doesn't enable that out of the box?
It would be really handy to use the <dialog> element it is so simple. But I can't because Firefox doesn't support it, which makes it boring and tedious for me as a web developer.
Also Firefox didn't support input type date, but they finally are adding support for it in Firefox 55.
I think Chrome has better developer tooling support for Server-Sent Events (SSE) though, and perhaps WebSockets.
Comment
-
Originally posted by uid313 View Post
As a web developer I come across nice features which would make things easy for me, but then I can't use them because they don't work in Firefox.
It would be really handy to use the <dialog> element it is so simple. But I can't because Firefox doesn't support it, which makes it boring and tedious for me as a web developer.
Also Firefox didn't support input type date, but they finally are adding support for it in Firefox 55.
I think Chrome has better developer tooling support for Server-Sent Events (SSE) though, and perhaps WebSockets.
Don't get me wrong, as a developer I know how crappy it is when you stumble upon a little gem only to have caniuse tell you "no, you can't". And I'd also say having a workable dialog is even more important than the support for time/date. But in this case it seems you're just lashing out at FF for no good reason.
Comment
Comment