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).
User contributions for Hixie
Jump to navigation
Jump to search
9 February 2011
- 20:2520:25, 9 February 2011 diff hist −768 Objections against CP for ISSUE-129 →Objections to basis for addition of "Guidance for User Agents"
- 20:2520:25, 9 February 2011 diff hist +520 Objections against CP for ISSUE-129 →Objections to basis for the img elements defualt role being img [sic]
- 20:2120:21, 9 February 2011 diff hist +1 Objections against CP for ISSUE-129 →Objections to basis for the img elements deualt role being img [sic]
- 20:2020:20, 9 February 2011 diff hist −787 Objections against CP for ISSUE-129 →Objections to basis for addition of "WAI-ARIA and HTML5 Attributes" table
- 20:1920:19, 9 February 2011 diff hist +1,154 Objections against CP for ISSUE-129 →Objections to basis for changes to allowed roles on the a element
- 20:1320:13, 9 February 2011 diff hist +1,941 Objections against CP for ISSUE-129 →Objections to basis for changes to allowed roles on the a element
- 19:5719:57, 9 February 2011 diff hist +489 Objections against CP for ISSUE-129 →Objections to basis for defining h1 to h6 element that does have an hgroup ancestor
- 19:4219:42, 9 February 2011 diff hist −960 Objections against CP for ISSUE-129 →Objections to basis for addition the merging of the tables in the current spec text [sic]
- 19:3519:35, 9 February 2011 diff hist −2,073 Objections against CP for ISSUE-129 →Process objections
7 February 2011
- 17:5117:51, 7 February 2011 diff hist +546 Change Proposal for ISSUE-140 →Restrictions on Applicable Specifications
- 09:4009:40, 7 February 2011 diff hist +468 N Objections against CPs for ISSUE-140 Created page with '* There is no use case that actually gets satisfied by this suggestion. ** In particular, the obvious use case of "a way to get a common understanding with someone else so that y...'
- 01:4901:49, 7 February 2011 diff hist +845 Change Proposal for ISSUE-140 →Rationale
6 February 2011
- 21:5521:55, 6 February 2011 diff hist +2,152 Change Proposal for ISSUE-150 No edit summary
- 21:4221:42, 6 February 2011 diff hist +546 Change Proposal for ISSUE-150 →Rationale
27 January 2011
- 00:0900:09, 27 January 2011 diff hist +1,680 FAQ →Isn’t the whole point of a specification to establish fixed point of reference so that all parties implementing the standard can ensure they have a common baseline of compatibility?
- 00:0700:07, 27 January 2011 diff hist +137 FAQ →How will anything be deprecated and removed if there are no version numbers?
26 January 2011
- 20:3120:31, 26 January 2011 diff hist −1 Main Page No edit summary
25 January 2011
- 20:2220:22, 25 January 2011 diff hist 0 Specs No edit summary
21 January 2011
- 23:0523:05, 21 January 2011 diff hist +1,236 FAQ →How can web developers know which features are safe to use?
- 22:5122:51, 21 January 2011 diff hist +193 FAQ →What does "Living Standard" mean?
- 22:4922:49, 21 January 2011 diff hist +786 FAQ →How about support in browsers for previous versions of this “living” HTML standard?
- 22:4522:45, 21 January 2011 diff hist +37 FAQ →How are developers to determine when certain parts of their pages will become invalid?
- 22:4422:44, 21 January 2011 diff hist +5 FAQ →Will HTML become an unusable mess as features are removed and old valid documents suddenly become invalid, if there are no version numbers?
- 22:4322:43, 21 January 2011 diff hist +4 FAQ →Will HTML become a bloated unimplementable mess as old features pile up if there are no version numbers?
- 22:4322:43, 21 January 2011 diff hist −25 FAQ →How will anything be deprecated and removed if there are no version numbers?
- 22:4222:42, 21 January 2011 diff hist +168 FAQ →How will anything be deprecated and removed if there are no version numbers?
- 22:4222:42, 21 January 2011 diff hist +1,389 FAQ →How are developers to determine when certain parts of their pages will become invalid?
- 22:3222:32, 21 January 2011 diff hist +55 FAQ →How are developers to determine when certain parts of their pages will become invalid?
- 22:3222:32, 21 January 2011 diff hist +143 FAQ →How are developers to determine when certain parts of their pages will become invalid?
- 22:3122:31, 21 January 2011 diff hist +506 FAQ →How do we know what to use, without having some sort of snapshot that browsers can aim at and developers can evaluate?
- 22:2822:28, 21 January 2011 diff hist +1 FAQ →How do we know what to use, without having some sort of snapshot that browser can aim at and developers can evaluate?
- 22:2622:26, 21 January 2011 diff hist +715 FAQ No edit summary
- 22:2122:21, 21 January 2011 diff hist +558 FAQ →How can web developers know which features are safe to use?
- 21:2621:26, 21 January 2011 diff hist 0 FAQ →If you do not publish snapshots every now and again, you are Orwellian in your recognition of the role the mistakes of the past play into the present and the future.
- 21:2621:26, 21 January 2011 diff hist −2 FAQ →If you do not publish snapshots every now and again, you are Orwellian in your recognition of the role the mistakes of the past play into the present and the future.
- 21:2621:26, 21 January 2011 diff hist +1 FAQ →How can web developers know which features are safe to use?
- 21:2521:25, 21 January 2011 diff hist −2 FAQ →This means you will only able to add to a spec, not redefine it.
- 21:2521:25, 21 January 2011 diff hist +2 FAQ →This means you will only able to add to a spec, not redefine it.
- 21:2521:25, 21 January 2011 diff hist −2 FAQ →This means you will only able to add to a spec, not redefine it.
- 21:2521:25, 21 January 2011 diff hist +207 FAQ →How about support in browsers for previous versions of this “living” HTML standard?
- 21:2221:22, 21 January 2011 diff hist +812 FAQ →The WHATWG Process
- 21:1821:18, 21 January 2011 diff hist +416 FAQ No edit summary
- 21:1521:15, 21 January 2011 diff hist +114 FAQ →“Living specification” sounds like a draft that may and will change at any moment and is probably not even complete at any moment of time...
- 21:1221:12, 21 January 2011 diff hist +26 FAQ →“Living specification” sounds like a draft that may and will change at any moment and is probably not even complete at any moment of time...
- 21:1121:11, 21 January 2011 diff hist +621 FAQ No edit summary
- 20:4820:48, 21 January 2011 diff hist +1,076 FAQ →The WHATWG Process
20 January 2011
- 17:0917:09, 20 January 2011 diff hist +9 Change Proposal for ISSUE-120 No edit summary
- 07:1307:13, 20 January 2011 diff hist +36 FAQ →What are the various versions of the spec?
- 07:1207:12, 20 January 2011 diff hist −295 FAQ →What are the various versions of the spec?
- 07:0407:04, 20 January 2011 diff hist −49 FAQ →What are the various versions of the spec?
- 06:5006:50, 20 January 2011 diff hist +2,473 FAQ No edit summary
- 05:0105:01, 20 January 2011 diff hist +366 FAQ No edit summary
- 04:4404:44, 20 January 2011 diff hist +864 FAQ No edit summary
- 04:2104:21, 20 January 2011 diff hist −402 FAQ No edit summary
19 January 2011
- 20:4920:49, 19 January 2011 diff hist +31 Change Proposal for ISSUE-120 →Risk
- 20:3520:35, 19 January 2011 diff hist −58 Change Proposal for ISSUE-120 →Negative Effects
- 18:4418:44, 19 January 2011 diff hist +200 Change Proposal for ISSUE-120 →Negative Effects
- 18:3918:39, 19 January 2011 diff hist +166 Change Proposal for ISSUE-120 →Other technologies
- 17:1517:15, 19 January 2011 diff hist +68 Change Proposal for ISSUE-120 →Cognitive difficulty
- 08:1108:11, 19 January 2011 diff hist −149 Change Proposal for ISSUE-120 →References
- 08:1008:10, 19 January 2011 diff hist +323 Change Proposal for ISSUE-120 →Impact
- 08:0508:05, 19 January 2011 diff hist +424 Change Proposal for ISSUE-120 →Cognitive difficulty
- 08:0308:03, 19 January 2011 diff hist +708 Change Proposal for ISSUE-120 →Other technologies
- 07:5607:56, 19 January 2011 diff hist −77 Change Proposal for ISSUE-120 →Cognitive difficulty
- 07:4707:47, 19 January 2011 diff hist +209 Change Proposal for ISSUE-120 →Cognitive difficulty
- 07:3207:32, 19 January 2011 diff hist +600 Change Proposal for ISSUE-120 →Other technologies
- 07:1307:13, 19 January 2011 diff hist +1,522 Change Proposal for ISSUE-120 No edit summary
- 06:5406:54, 19 January 2011 diff hist +263 Change Proposal for ISSUE-120 →Intentional misimplementation
- 06:5106:51, 19 January 2011 diff hist +758 Change Proposal for ISSUE-120 →Rationale
- 04:0704:07, 19 January 2011 diff hist +2 Change Proposal for ISSUE-129 No edit summary
- 02:5102:51, 19 January 2011 diff hist +169 Change Proposal for ISSUE-120 No edit summary
- 02:5002:50, 19 January 2011 diff hist +268 Change Proposal for ISSUE-120 →Rationale
- 02:4802:48, 19 January 2011 diff hist +42 Change Proposal for ISSUE-120 →Cognitive difficulty
- 02:4702:47, 19 January 2011 diff hist 0 Change Proposal for ISSUE-120 →Cognitive difficulty
- 02:4702:47, 19 January 2011 diff hist +646 Change Proposal for ISSUE-120 →Cognitive difficulty
- 02:3602:36, 19 January 2011 diff hist +3,485 Change Proposal for ISSUE-120 →Rationale
- 02:2702:27, 19 January 2011 diff hist +1,286 Change Proposal for ISSUE-120 →Rationale
18 January 2011
- 23:1723:17, 18 January 2011 diff hist +1,445 Change Proposal for ISSUE-120 →Details
- 22:4322:43, 18 January 2011 diff hist +264 N Change Proposal for ISSUE-120 Created page with '== Summary == Simplify the specification by removing features that are documented to be confusing to users. __TOC__ == Rationale == == Details == == Impact == === Positive ...'
17 January 2011
- 21:1621:16, 17 January 2011 diff hist +7 Objections against CP for ISSUE-129 →Title and introduction
- 21:1521:15, 17 January 2011 diff hist +259 Objections against CP for ISSUE-129 →Objections to the proposed text
- 21:1321:13, 17 January 2011 diff hist +18 Objections against CP for ISSUE-129 →Process objections
- 09:5609:56, 17 January 2011 diff hist 0 Change Proposal for ISSUE-129 →Rationale
- 09:5509:55, 17 January 2011 diff hist 0 Change Proposal for ISSUE-129 →Bug 10903: Requesting more introductory text
- 09:5509:55, 17 January 2011 diff hist −91 Change Proposal for ISSUE-129 →Objections to the other change proposal
- 09:3509:35, 17 January 2011 diff hist +30 Change Proposal for ISSUE-129 →Bug 10903: Requesting more introductory text
- 09:3509:35, 17 January 2011 diff hist +67 Change Proposal for ISSUE-129 →Bug 10594: Move some requirements regarding ARIA attributes into a separate table
- 09:3209:32, 17 January 2011 diff hist +68 Change Proposal for ISSUE-129 →Bug 10592: Request regarding the ARIA role of heading elements inside HGROUP elements
- 00:5100:51, 17 January 2011 diff hist +238 Change Proposal for ISSUE-129 →Bug 10449: Allow an H1 element to be described as a spinbutton or checkbox, etc
16 January 2011
- 08:2708:27, 16 January 2011 diff hist +142 Change Proposal for ISSUE-129 →Why use cases are needed to justify allowing particular roles in particular situations
- 07:4507:45, 16 January 2011 diff hist +62 Objections against CP for ISSUE-129 →Objections to Guiding factors for decisions on ARIA Role use
- 07:4307:43, 16 January 2011 diff hist +1,473 Objections against CP for ISSUE-129 →Objections to basis for allowing roles on heading elements (H1-H6)
- 07:3407:34, 16 January 2011 diff hist +1,260 Objections against CP for ISSUE-129 →Objections to basis for changes to command roles
- 06:4706:47, 16 January 2011 diff hist +543 Change Proposal for ISSUE-129 →Bug 10493: Requesting additional prose in the HTML spec stating that certain roles defined in the ARIA spec have restrictions on their use defined in the ARIA spec
- 06:3906:39, 16 January 2011 diff hist −6 Change Proposal for ISSUE-129 →Rationale
- 06:3806:38, 16 January 2011 diff hist +1 Change Proposal for ISSUE-129 →Bugs 8000 and 10448: Allow links to be described as scroll bars, buttons to be described as progress bars, etc
- 06:3806:38, 16 January 2011 diff hist −5 Change Proposal for ISSUE-129 →Bugs 8000 and 10448: Allow links to be described as scroll bars, buttons to be described as progress bars, etc
- 06:3806:38, 16 January 2011 diff hist +1 Change Proposal for ISSUE-129 →Bugs 8000 and 10448: Allow links to be described as scroll bars, buttons to be described as progress bars, etc
- 06:3806:38, 16 January 2011 diff hist +127 Change Proposal for ISSUE-129 →Bug 10448: Allow links to be described as scroll bars, buttons to be described as progress bars, etc
- 06:3706:37, 16 January 2011 diff hist −167 Change Proposal for ISSUE-129 →Bug 8000: Allow authors to use elements in ways that contradict their semantics