5 ms·

If that's the case: 1a) Why would it matter that Microsoft, Google, Mozilla, and/or Apple object to W3C DOM 4.1 if they don't implement it? 1b) Why would Micr

by jsgo 9y ago

If that's the case: 1a) Why would it matter that Microsoft, Google, Mozilla, and/or Apple object to W3C DOM 4.1 if they don't implement it? 1b) Why would Microsoft, Google, Mozilla, and/or Apple care enough to object to W3C DOM 4.1 if they aren't implementing it? Why would they even give any effort to a competing specification and just allow it to die from inactivity? 2) Why does what is in W3C DOM 4.1 matter if the high 90s percentage of users are served by a browser in the WHATWG DOM camp? This could probably be condensed down to "Why do W3C's specifications matter at all" really.

saas_co_de 9y ago
Exactly. They don't want any competing products so preventing the development of a standard they don't control is obvious.
- cwyers 9y ago
  If this is about preventing competition in the browser space, then why doesn't one of the browser makers with lower market share defect from Google's position?
dragonwriter 9y ago
> Why would it matter that Microsoft, Google, Mozilla, and/or Apple object to W3C DOM 4.1 if they don't implement it? It matters to the utility of the W3C DOM spec that it doesn't represent either what browsers have implemented or what they will implement. > Why would Microsoft, Google, Mozilla, and/or Apple care enough to object to W3C DOM 4.1 if they aren't implementing it? They care enough because they want the W3C, if it is going to write purported web standards, to do something that won't confuse developers and lead to browser vendors fielding complaints from developers who mistake useless W3C documents for something meaningful. > Why would they even give any effort to a competing specification and just allow it to die from inactivity? They don't want to have a competing specification, though they do not seem opposed to having a specification with a different focus but consistent with WHATWG to the degree dictate by the purpose.) > Why does what is in W3C DOM 4.1 matter if the high 90s percentage of users are served by a browser in the WHATWG DOM camp? The idea is not to have opposing camps, though if W3C insists on making it an opposing camps situation, thst becomes a real issue.

by jsgo 9y ago

saas_co_de 9y ago

Exactly. They don't want any competing products so preventing the development of a standard they don't control is obvious.

cwyers 9y ago
If this is about preventing competition in the browser space, then why doesn't one of the browser makers with lower market share defect from Google's position?

dragonwriter 9y ago

> Why would it matter that Microsoft, Google, Mozilla, and/or Apple object to W3C DOM 4.1 if they don't implement it? It matters to the utility of the W3C DOM spec that it doesn't represent either what browsers have implemented or what they will implement. > Why would Microsoft, Google, Mozilla, and/or Apple care enough to object to W3C DOM 4.1 if they aren't implementing it? They care enough because they want the W3C, if it is going to write purported web standards, to do something that won't confuse developers and lead to browser vendors fielding complaints from developers who mistake useless W3C documents for something meaningful. > Why would they even give any effort to a competing specification and just allow it to die from inactivity? They don't want to have a competing specification, though they do not seem opposed to having a specification with a different focus but consistent with WHATWG to the degree dictate by the purpose.) > Why does what is in W3C DOM 4.1 matter if the high 90s percentage of users are served by a browser in the WHATWG DOM camp? The idea is not to have opposing camps, though if W3C insists on making it an opposing camps situation, thst becomes a real issue.