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
8 March 2011
- 07:1607:16, 8 March 2011 diff hist +155 Web ECMAScript →Property Enumeration
14 February 2011
- 09:1409:14, 14 February 2011 diff hist −1,607 Change Proposal for ISSUE-127 Replaced content with 'Latest draft is at: http://lists.w3.org/Archives/Public/public-html/2011Feb/0243.html'
- 09:0809:08, 14 February 2011 diff hist +1,692 N Objections against CPs for ISSUE-127 Created page with '* Fundamentally, the change here is editorial, and should be left up to editorial discretion. The suggested change is to a non-normative table, and despite claims to the contrary...'
- 09:0509:05, 14 February 2011 diff hist +332 Change Proposal for ISSUE-127 No edit summary
- 09:0009:00, 14 February 2011 diff hist +1,018 Change Proposal for ISSUE-127 No edit summary
- 08:5108:51, 14 February 2011 diff hist +342 N Change Proposal for ISSUE-127 Created page with ' * There is no "goal to make link relations handling inside HTML consistent with link relations in other contexts". There is no particular benefit or use case to making link rela...'
9 February 2011
- 20:3520:35, 9 February 2011 diff hist −16 Objections against CP for ISSUE-129 No edit summary
- 20:3220:32, 9 February 2011 diff hist −7,137 Objections against CP for ISSUE-129 →Objections to the proposed text
- 20:3120:31, 9 February 2011 diff hist +120 Objections against CP for ISSUE-129 →Objections to Guiding factors for decisions on ARIA Role use
- 20:2720:27, 9 February 2011 diff hist −304 Objections against CP for ISSUE-129 →Objections to basis for addition of "References"
- 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?