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
(Created page with 'This is a list of cases where publication of specs at TR/ hurt. * https://bugzilla.mozilla.org/show_bug.cgi?id=688878 * https://bugzilla.mozilla.org/show_bug.cgi?id=505115#c141') |
No edit summary |
||
| Line 1: | Line 1: | ||
This is a list of cases where publication of specs | This is a list of cases where publication of specs on the TR/ page hurt. | ||
* https://bugzilla.mozilla.org/show_bug.cgi?id=688878 | * https://bugzilla.mozilla.org/show_bug.cgi?id=688878 | ||
* https://bugzilla.mozilla.org/show_bug.cgi?id=505115#c141 | * https://bugzilla.mozilla.org/show_bug.cgi?id=505115#c141 | ||
* 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 overridden by one spec (CSS regions) were used by the proposal, without the implications being understood. (Specifically, apparently CSS regions redefines how the containing block mechanism works.) | |||
Revision as of 23:08, 3 April 2012
This is a list of cases where publication of specs on the TR/ page hurt.
- https://bugzilla.mozilla.org/show_bug.cgi?id=688878
- https://bugzilla.mozilla.org/show_bug.cgi?id=505115#c141
- 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 overridden by one spec (CSS regions) were used by the proposal, without the implications being understood. (Specifically, apparently CSS regions redefines how the containing block mechanism works.)