A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
W3C: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Some issues with the W3C. Not really exhaustive. | |||
* https://bugzilla.mozilla.org/show_bug.cgi?id=688878 | * Restrictive copyright | ||
* https://bugzilla.mozilla.org/show_bug.cgi?id=505115#c141 | * Forks rather than cooperates | ||
* When designing the Fullscreen/<dialog> stacking model, the lack of a living standard spec for CSS that represented the current cutting edge status meant that features of CSS that were may have been overridden by one spec (e.g. CSS regions) were used by the proposal, without the implications being understood. (Specifically, it was suggested that CSS regions redefined how the containing block mechanism works; in general, without knowing what all the relevant specs are, there is no way to be sure that no other spec does in fact modify some underlying concept.) | * Main publications on TR/ are stale and cause confusion | ||
** https://bugzilla.mozilla.org/show_bug.cgi?id=688878#c6 | |||
** https://bugzilla.mozilla.org/show_bug.cgi?id=505115#c141 | |||
** http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/1207.html | |||
** https://critic.hoppipolla.co.uk/showcomment?chain=1232 | |||
** http://lists.w3.org/Archives/Public/public-w3process/2014Sep/0081.html | |||
** ?? many versions of canvas | |||
* CSS modularization (When designing the Fullscreen/<dialog> stacking model, the lack of a living standard spec for CSS that represented the current cutting edge status meant that features of CSS that were may have been overridden by one spec (e.g. CSS regions) were used by the proposal, without the implications being understood. (Specifically, it was suggested that CSS regions redefined how the containing block mechanism works; in general, without knowing what all the relevant specs are, there is no way to be sure that no other spec does in fact modify some underlying concept.)) | |||
[[Category:Spec_coordination]] | [[Category:Spec_coordination]] | ||
Revision as of 10:59, 12 September 2014
Some issues with the W3C. Not really exhaustive.
- Restrictive copyright
- Forks rather than cooperates
- Main publications on TR/ are stale and cause confusion
- https://bugzilla.mozilla.org/show_bug.cgi?id=688878#c6
- https://bugzilla.mozilla.org/show_bug.cgi?id=505115#c141
- http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/1207.html
- https://critic.hoppipolla.co.uk/showcomment?chain=1232
- http://lists.w3.org/Archives/Public/public-w3process/2014Sep/0081.html
- ?? many versions of canvas
- CSS modularization (When designing the Fullscreen/<dialog> stacking model, the lack of a living standard spec for CSS that represented the current cutting edge status meant that features of CSS that were may have been overridden by one spec (e.g. CSS regions) were used by the proposal, without the implications being understood. (Specifically, it was suggested that CSS regions redefined how the containing block mechanism works; in general, without knowing what all the relevant specs are, there is no way to be sure that no other spec does in fact modify some underlying concept.))