6 ms·

Interesting, as a web developer I really really want Servo to become a big success. I wonder at what point do Mozilla think I should start having a once over i

Interesting, as a web developer I really really want Servo to become a big success. I wonder at what point do Mozilla think I should start having a once over in Servo before putting my sites on the web? Why not, I'll start doing this as it can't do any harm and create some test cases should I find some weirdness. It's really easy to build a copy of servo after all: https://github.com/servo/servo The instructions there generally just work.

pcwalton 11y ago
Don't contort your Web sites to work around brokenness in Servo; just file bugs. Rendering bugs are our bugs, not yours :)
- Stormcaller 11y ago
  I wonder if there was an idea of a "strict mode" at any point? When making sure every site works surely you guys will have to render invalid code "correctly", I assume. For example I am willing to develop in your browser if it meant I wouldn't broke some rules and the browser would care about that. Of course html validators exist and browsers display invalid css in their inspectors but I am asking for something like that would expect valid code. throw an error in my face if I didn't close a html tag or used an invalid css value, at any point. Like if a javascript code resulted in my page getting invalid layout then browser could yell at me that causes an invalid layout. Maybe even a small performance improvement if my code conformed to every layout rule.
  - andy_ppp 11y ago
    Yes! A nice idea that... as has been previously mentioned XHTML failed due to there already being a version of the same thing with tonnes of automatic error handling built in! Which one will be most popular; a programming language that always seemed to complain and display an error, or one that 99% of the time corrected your mistakes for you.
  - Tobu 11y ago
    xhtml worked like that, html5 has moved towards specifying the quirks that are used to deal with poor conformance. That said, if you look at a webdev console, things that cause poor performance (à la document.write) tend to be noted.
serge2k 11y ago
and I get build failures on osx. :( I just wanted to play with it anyway.
- pcwalton 11y ago
  Please file bugs!

pcwalton 11y ago

Don't contort your Web sites to work around brokenness in Servo; just file bugs. Rendering bugs are our bugs, not yours :)

Stormcaller 11y ago
I wonder if there was an idea of a "strict mode" at any point? When making sure every site works surely you guys will have to render invalid code "correctly", I assume. For example I am willing to develop in your browser if it meant I wouldn't broke some rules and the browser would care about that. Of course html validators exist and browsers display invalid css in their inspectors but I am asking for something like that would expect valid code. throw an error in my face if I didn't close a html tag or used an invalid css value, at any point. Like if a javascript code resulted in my page getting invalid layout then browser could yell at me that causes an invalid layout. Maybe even a small performance improvement if my code conformed to every layout rule.
- andy_ppp 11y ago
  Yes! A nice idea that... as has been previously mentioned XHTML failed due to there already being a version of the same thing with tonnes of automatic error handling built in! Which one will be most popular; a programming language that always seemed to complain and display an error, or one that 99% of the time corrected your mistakes for you.
- Tobu 11y ago
  xhtml worked like that, html5 has moved towards specifying the quirks that are used to deal with poor conformance. That said, if you look at a webdev console, things that cause poor performance (à la document.write) tend to be noted.

serge2k 11y ago

and I get build failures on osx. :( I just wanted to play with it anyway.

pcwalton 11y ago
Please file bugs!