4 ms·

"The WHATWG was founded by individuals from Apple Inc., the Mozilla Foundation and Opera Software" Steering group is people from the 4 major companies. At lea

"The WHATWG was founded by individuals from Apple Inc., the Mozilla Foundation and Opera Software" Steering group is people from the 4 major companies. At least originally WHATWG was undeniably and undisputedly a good thing. Their work literally removed incompatibilities from the web by producing standards that specify how HTML should actually be rendered, for example. Now everything is subverted and co-opted by Google, of course.

andrewmcwatters 4y ago
> Their work literally removed incompatibilities from the web by producing standards that specify how HTML should actually be rendered, for example. No they didn't. There's no standard today that exists that describes the implementation level details of CSS 2.1. It's descriptive and you have to figure it out yourself. // 2.3 The CSS 2.1 processing model // This section up to but not including its subsections is non-normative. // This section presents one possible model of how user agents that // support CSS work. This is only a conceptual model; real implementations // may vary.
- dmitriid 4y ago
  I talked about HTML, not CSS. CSS is a separate standard, outside of purview of WHATWG
  - andrewmcwatters 4y ago
    HTML rendering is a part of the visual user agent standard in CSS 2.1. It is no longer outside of their purview when they discuss visual output. The HTML issue tracker also discusses changes to JavaScript APIs, among other things. So, emphatically no they did not "remove incompatibilities from the web by producing standards that specify how HTML should actually be rendered." That's the CSS specification's job. Here are all of the standards WHATWG works on: https://spec.whatwg.org/ https://spec.whatwg.org/ They also discuss changes to standards they don't work on directly, but effect change through the HTML Living Standard.

andrewmcwatters 4y ago

> Their work literally removed incompatibilities from the web by producing standards that specify how HTML should actually be rendered, for example. No they didn't. There's no standard today that exists that describes the implementation level details of CSS 2.1. It's descriptive and you have to figure it out yourself. // 2.3 The CSS 2.1 processing model // This section up to but not including its subsections is non-normative. // This section presents one possible model of how user agents that // support CSS work. This is only a conceptual model; real implementations // may vary.

dmitriid 4y ago
I talked about HTML, not CSS. CSS is a separate standard, outside of purview of WHATWG
- andrewmcwatters 4y ago
  HTML rendering is a part of the visual user agent standard in CSS 2.1. It is no longer outside of their purview when they discuss visual output. The HTML issue tracker also discusses changes to JavaScript APIs, among other things. So, emphatically no they did not "remove incompatibilities from the web by producing standards that specify how HTML should actually be rendered." That's the CSS specification's job. Here are all of the standards WHATWG works on: https://spec.whatwg.org/ https://spec.whatwg.org/ They also discuss changes to standards they don't work on directly, but effect change through the HTML Living Standard.