Tuesday, 31 January 2012
- Re: Hidden file inputs [Was: Revert Request]
- Re: HTML5 and Speech Input
- Re: Using an image map for long described image links [Was: Revert Request]
- Hidden file inputs [Was: Revert Request]
- Re: Revert Request
- Re: Revert Request
- Re: document.write() and .close() allowed on IFRAME though its document.domain was set
- Re: document.write() and .close() allowed on IFRAME though its document.domain was set
- HTML5 and Speech Input
- Hyperlink and Metadata
- Re: Revert Request
- Re: Revert Request
- [Bug 15809] New: ".... The root element of this tree is the html element..." DOM Trees have nodes not elementes. HTML documents have elements and text.
Sunday, 29 January 2012
Tuesday, 31 January 2012
- Re: Using an image map for long described image links [Was: Revert Request]
- Re: Revert Request
- Re: Revert Request
- Re: [html5] inline table
- Re: Revert Request
Monday, 30 January 2012
- Using an image map for long described image links [Was: Revert Request]
- Re: Revert Request
- Re: [html5] inline table
- Re: [html5] inline table
- Re: [html5] inline table
- Re: Fw: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: [html5] inline table
- Re: [html5] inline table
- Re: [html5] inline table
- [html5] inline table
Sunday, 29 January 2012
Saturday, 28 January 2012
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- RE: Revert Request
Friday, 27 January 2012
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
Thursday, 26 January 2012
Friday, 27 January 2012
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- RE: Fw: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: ISSUE-195: form-http-req - Chairs Solicit Proposals
- Re: Revert Request
- Re: Revert Request
- Re: Revert Request
- Re: Fw: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Revert Request
- Re: Accessibility APIs (was RE: Revert Request)
- Accessibility APIs (was RE: Revert Request)
- Re: Revert Request
- RE: Revert Request
- RE: Fw: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Meta element to prevent resending post data
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- RE: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
Thursday, 26 January 2012
- RE: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Re: Meta element to prevent resending post data
- Meta element to prevent resending post data
- Re: Revert Request
- Re: ISSUE-195: form-http-req - Chairs Solicit Proposals
- RE: Revert Request
- [Bug 15730] New: Suggestion: Introduce "content" element
- Re: Revert Request
- Re: Revert Request
- Re: Revert Request
- Re: Revert Request
- Revert Request
- [Bug 15723] New: There needs to be a way to indicate what type of abbreviation is wrapped in an abbr element. The problem I am trying to solve: Proper indication to screen readers of the type of abbreviation so that the screen reader does not have to guess at what it shou
Wednesday, 25 January 2012
- [Bug 15718] New: Need to decide if URLs can ever fail to parse
- Re: CfC: Close ISSUE-177: ietf-id-wip by Amicable Resolution
- RE: CfC: Close ISSUE-177: ietf-id-wip by Amicable Resolution
- RE: Close ISSUE-181: remov-sidebar by Amicable Resolution
- RE: Close ISSUE-180: allowpopups by Amicable Resolution
- ISSUE-192: title-attribute - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-191: ins-del - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-190: coding-example - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-187: validity-stability - Chairs Solicit Alternate Proposals or Counter-Proposals
- [Bug 15704] New: HTMLFormElement::elements is not compatible with existing UAs
- [Bug 15703] New: ":required" pseudo selector for a radio button group
Tuesday, 24 January 2012
- [Bug 15701] New: text "if none of the ancestors" is presumably not exactly correct
- [Bug 15700] New: appcache: Prevent sensitive data from being cached
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- [Bug 15683] New: It is very tedious and almost impossible to properly display poetry that is typographically metered, specially in Arabic since it needs strict typographical alignments. The fact that Arabic readers almost always come across poetry on daily bases as they b
Friday, 20 January 2012
Monday, 23 January 2012
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- Re: Revised Timeline and New Bug Priority Policy
Sunday, 22 January 2012
- RE: HTML5 Citations, References, Equation References and Footnotes
- Re: HTML5 Citations, References, Equation References and Footnotes
Saturday, 21 January 2012
Friday, 20 January 2012
- Re: ISSUE-187: validity-stability - Chairs Solicit Proposals
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- Re: proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- proposal for ISSUE-191: replace ins and del elements by an attibute-based solution
- [Bug 15638] New: what to do to check the browser's html5 compatibility
Thursday, 19 January 2012
- [Bug 15630] New: update ORIGIN reference
- [Bug 15627] New: Xmpp missing from whitelist of URI schemes
- RE: Revised Timeline and New Bug Priority Policy
- Re: Change Proposal for ISSUE-177, was: ISSUE-177 ietf-id-wip: Chairs Solicit Proposals
- Re: Revised Timeline and New Bug Priority Policy
- RE: Revised Timeline and New Bug Priority Policy
- ISSUE-203: media-descriptions - Chairs Solicit Proposals
Wednesday, 18 January 2012
- [Bug 15607] New: WF2: Change accept="" to accept file extensions as well as MIME types (maybe based on whether they start with a period)
- [Bug 15606] New: clarification of TextTrackCue.getCueAsHTML() conversion rules
- [Bug 15604] New: TextTrackCue.getCueAsHTML() incorrectly marked as mutable
- Re: ISSUE-196: ua-http-resp-handling - Chairs Solicit Proposals
- Re: ISSUE-195: form-http-req - Chairs Solicit Proposals
- New Issue Request: All Media Elements should have the ability to have both short and longer textual descriptions associated to the element
- Issue 190 change proposal - Replace poor coding example for figure containing multiple images
Tuesday, 17 January 2012
- [Bug 15596] New: option.value IDL attribute should return |text| IDL attribute instead of |textContent| when no value is set
- [Bug 15592] New: Feature Request: A javax.smartcardio alternative
Monday, 16 January 2012
Wednesday, 18 January 2012
Tuesday, 17 January 2012
- ISSUE-189: uri-web-prefix - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-188: generic-track-format - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-182: footnote-recommendation - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-185: drop-pubdate - Chairs Solicit Alternate Proposals or Counter-Proposals
- RE: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals
- ISSUE-202: figcaption-words - Chairs Solicit Proposals
- ISSUE-201: canvas-fallback - Chairs Solicit Proposals
- ISSUE-200: legend-placement - Chairs Solicit Proposals
- ISSUE-199: aria-processing - Chairs Solicit Proposals
- ISSUE-198: innerHTML-patent-policy - Chairs Solicit Proposals
- ISSUE-192: title attribute definition does not match reality - change proposal
Monday, 16 January 2012
- Re: ISSUE-186: role-presentation-override - Chairs Solicit Proposals
- ISSUE-197: accept-file-ext - Chairs Solicit Proposals
- ISSUE-194: full-transcript - Chairs Solicit Proposals
- ISSUE-196: ua-http-resp-handling - Chairs Solicit Proposals
- ISSUE-195: form-http-req - Chairs Solicit Proposals
- ISSUE-193: inaccessible-example - Chairs Solicit Proposals
Saturday, 14 January 2012
Wednesday, 11 January 2012
- [Bug 15526] New: Nitpick / clarification request: Navigation to fragment identifier doesn't specify value of non-optional "align to top flag" "When the user agent is required to scroll to the fragment identifier, it must change the scrolling position of the document using
- [Bug 15520] New: In 1.2 I see example: <h1 itemscope> <data itemprop="product-id" value="9678AOU879">The Instigator 2000</data> </h1> Here, there is an item with a property whose value is a product ID. The ID is not human-friendly, so the product's name is used the human
Sunday, 15 January 2012
Saturday, 14 January 2012
- Re: noted 3 issues re: time/data (was Re: minutes for HTML WG f2f, 2011-11-04, part 1)
- Change Proposal for ISSUE-189, was: ISSUE-189: uri-web-prefix - Chairs Solicit Proposals
Friday, 13 January 2012
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- RE: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: HTML5 design philosophy disconnect
- Re: ISSUE-186: role-presentation-override - Chairs Solicit Proposals
- Goodbye
Thursday, 12 January 2012
Friday, 13 January 2012
Thursday, 12 January 2012
- Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals
- Re: Ruby markup in html5
- Ruby markup in html5
- {agenda} HTML WG telecon 2012-01-12: issue progress, other business
- Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals
- Re: ISSUE-186: role-presentation-override - Chairs Solicit Proposals
- Re: ISSUE-186: role-presentation-override - Chairs Solicit Proposals
- Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals
- Re: ISSUE-182: footnote-recommendation - Chairs Solicit Proposals
- ISSUE-183: enhance-time - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-186: role-presentation-override - Chairs Solicit Proposals
- ISSUE-179: av_param - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-172: restore-rb - Chairs Solicit Alternate Proposals or Counter-Proposals
- Re: ISSUE-172: restore-rb - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-184: data-element - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-131: caret-location-API - Chairs Solicit Proposals
- ISSUE-185: drop-pubdate - Chairs Solicit Alternate Proposals or Counter-Proposals
- ISSUE-172: restore-rb - Chairs Solicit Alternate Proposals or Counter-Proposals
- CfC: Close ISSUE-181: remov-sidebar by Amicable Resolution
- CfC: Close ISSUE-180: allowpopups by Amicable Resolution
Wednesday, 11 January 2012
- RE: Revised Timeline and New Bug Priority Policy
- [Bug 15513] New: section #4.9 Hello, is there any specific reason, why isn't posible, in html5 this? <!DOCTYPE html> <title>asd</title> <table> <tr> <form> <td> </td> </form> </tr> </table> browser can handle it OK thx
- [Bug 15512] New: Section: Links >> Link types; Requesting that the link type "publisher" be reinstated inside the HTML5 specification. The reason is because Google has adopted this tag as a means of identifying a web site with a corresponding Google+ business page. It is
Tuesday, 10 January 2012
- [Bug 15510] New: avoid minimized attributes
- RE: ISSUE-187: validity-stability - Chairs Solicit Proposals
- Re: ISSUE-172: restore-rb- Chairs Solicit Proposals
- [Bug 15488] New: it makes no sense to limit the placeholder attribute to values of the same direction as the <input>
- Re: ISSUE-187: validity-stability - Chairs Solicit Proposals
Monday, 9 January 2012
- Re: CfC: Close ISSUE-177: ietf-id-wip by Amicable Resolution
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
Sunday, 8 January 2012
- [Bug 15464] New: Since this page is very large and since it is referred to by other pages and since there already exists a multi page format Please evaluate having this page "http://dev.w3.org/html5/spec/Overview.html" be the multi page format version. Thank you for your
- [Bug 15465] New: Please add a comment on THIS page, where the availability of the "web developer edition" is mentioned, that the "web developer edition" is for "Web authors and others who are not User Agent implementors(spelling?)" which I would expect to be the majority
Saturday, 7 January 2012
Sunday, 8 January 2012
- Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
Saturday, 7 January 2012
Friday, 6 January 2012
- [Bug 15446] New: Hi, I suggest to create a breadcrum tag. It would be very useful. I also suggest a title property for sectioning elements. Why? Well, maybe I have section that because of aesthetic reasons I don't want it to have a title, so I don't use header tags, or a
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
- Re: HTML5 design philosophy disconnect
- HTML5 design philosophy disconnect
- [Bug 15438] New: Details node needs to fire event when opened or closed
- Re: Should script execution be allowed in designMode documents?
Thursday, 5 January 2012
- [Bug 15428] New: :read-write should always apply to input elements if @readonly doesn't apply
- [Bug 15429] New: Form submission: reveal submit button in submit event
- 2012
Wednesday, 4 January 2012
Tuesday, 3 January 2012
Monday, 2 January 2012
- [Bug 15380] New: Define a User-Agent string format subset (liason witth HTTP people etc)
- [Bug 15379] New: Hi, i was wondering why there is explicit hard limit of how setTimeout works. In spec it says: 6.3 Timers ... "4. If the currently running task is a task that was created by the setTimeout() method, and timeout is less than 4, then increase timeout to 4."