public-html-comments  

Messages by Thread

• Re: A Unified solution to <picture> Mathew Marquis
  • Re: A Unified solution to <picture> Nathanael D. Jones
  • Re: A Unified solution to <picture> Edward O'Connor
• Terminology: Inline, Embedded & External. Anthony Randhawa
• Re: Re: HTML5 Datalist Element and Input Element's List Attribute Dead on Arrival Altieres Del-Sent
• Re: input type alpha Jukka K. Korpela
• Proposals regarding <main> element Ian Yang
  • Re: Proposals regarding <main> element Ian Devlin
  • Re: Proposals regarding <main> element Ian Yang
  • Proposals regarding <main> element Ian Yang
  • Re: Proposals regarding <main> element TRON-DELTA.ORG
• Microdata HTML5 and schema.org vocab Vipul S. Chawathe
• Objection to Microdata Candidate Recommendation Steve Battle
  • Objection to Microdata Candidate Recommendation Young,Jeff (OR)
• No Microdata CR Alex Milowski
• Microdata published as a W3C Note instead of a W3C Rec William Greenly
• RDFa Lite Dennis Erny
  • Re: RDFa Lite Jukka K. Korpela
• Microdata as W3C Note vs. W3C Rec. Eric Franzon
  • Re: Microdata as W3C Note vs. W3C Rec. Clint Hill
  • Re: Microdata as W3C Note vs. W3C Rec. Nathan
  • Re: Microdata as W3C Note vs. W3C Rec. Brian Kardell
• Please don't push Microdata. RDFa is the way to go. Florian Bantner
• Concerns Regarding Microdata CR David Wood
  • Re: Concerns Regarding Microdata CR Gannon Dick
• Update [DOMCORE] Reference Menachem Salomon
• Re: longdesc spec review Laura Carlson
• HTML5 New Feature: CANVAS as a FORM INPUT Shai Manor
  • Re: HTML5 New Feature: CANVAS as a FORM INPUT Thomas A. Fine
  • Re: HTML5 New Feature: CANVAS as a FORM INPUT Charles Pritchard
• <code translate=no> Andreas Prilop
  • Re: <code translate=no> Jukka K. Korpela
  • Re: <code translate=no> Gannon Dick
  • Re: <code translate=no> Andreas Prilop
• General inner nesting has not been provided for hsv
• srcset proposal is not fully responsive? Marcos Caceres
  • Re: srcset proposal is not fully responsive? Edward O'Connor
  • Re: srcset proposal is not fully responsive? Marcos Caceres
• How much current HTML5 would remain as is? Dai Nish
• HTML5 Datalist Element and Input Element's List Attribute Dead on Arrival Nicholas Sloan
  • Re: HTML5 Datalist Element and Input Element's List Attribute Dead on Arrival Arthur Clifford
  • Re: HTML5 Datalist Element and Input Element's List Attribute Dead on Arrival Mounir Lamouri
• HTML5 longdesc Specification Laura Carlson
• aria-describedat (was Re: 48-Hour Consensus Call: InstateLongdesc CP Update) Laura Carlson
• The server in the middle problem and possible solutions Eduardo Robles Elvira
• Datalist pollute the DOM Fred .
  • Re: Datalist pollute the DOM Jason H
• Securing Password Inputs Jason H
  • Re: Securing Password Inputs Thomas A. Fine
  • Re: Securing Password Inputs Seth Call
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Arthur Clifford
  • Re: Securing Password Inputs Arthur Clifford
  • Re: Securing Password Inputs Thomas A. Fine
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Thomas A. Fine
  • Re: Securing Password Inputs Arthur Clifford
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Cameron Jones
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Seth Call
  • Re: Securing Password Inputs Jason H
  • Re: Securing Password Inputs Jason H
• code validation Darl McCleary
• Hhow can i create Feedback Comments Kh Hafizur Rahman
• HTML5 Spec Section 2.2.2 and the DOM Parsing and Serialization Spec T.J. Crowder
• HTML5: Techniques for providing useful text alternatives - Public Comment Alicia Landry
  • Re: HTML5: Techniques for providing useful text alternatives - Public Comment Laura Carlson
• Re: Comments on Image maps in HTML5, coordinate and possible validator issues Michael[tm] Smith
• Some advices for table, th and td elements River John
  • Re: Some advices for table, th and td elements Jukka K. Korpela
  • Re: Some advices for table, th and td elements Jason H
• Re: Using ARIA in HTML Joshue O Connor
  • Re: Using ARIA in HTML Steve Faulkner
• Anchor tags Shields,Dan
  • Re: Anchor tags T.J. Crowder
  • Re: Anchor tags Matthias Reuter
  • Re: Anchor tags Jukka K. Korpela
• Resistance of <keygen> to client-side attack Alan Egerton
  • Re: Resistance of <keygen> to client-side attack Anders Rundgren
  • Re: Resistance of <keygen> to client-side attack Alan Egerton
• [public-html-comments] <none> Ellen mcg
  • [public-html-comments] <none> Mariano Barbu
  • [public-html-comments] <none> Olivier DAVID
• Ellen mcg wants to chat Ellen mcg
• http://www.w3.org/TR/2012/WD-html5-20120329/ Ellen mcg
• Image Scaling for High-Pixel-Density (i.e. Retina) Displays - Re: -webkit-image-set and <image> Tom Penzer
  • Re: Image Scaling for High-Pixel-Density (i.e. Retina) Displays - Re: -webkit-image-set and <image> Jason H
  • Re: Image Scaling for High-Pixel-Density (i.e. Retina) Displays - Re: -webkit-image-set and <image> Tom Penzer
  • Re: Image Scaling for High-Pixel-Density (i.e. Retina) Displays - Re: -webkit-image-set and <image> Jason H
  • Re: Image Scaling for High-Pixel-Density (i.e. Retina) Displays - Re: -webkit-image-set and <image> Tom Penzer
  • Re: Image Scaling for High-Pixel-Density (i.e. Retina) Displays - Re: -webkit-image-set and <image> Arthur Clifford
  • Re: Image Scaling for High-Pixel-Density (i.e. Retina) Displays - Re: -webkit-image-set and <image> Tom Penzer
• Standard for geotagging video with video-frame metadata Bala Kammela
• RE: Ref: HTML to Platform Accessibility APIs Implementation Guide Steve Faulkner
• Incorrect contact email id: Comments on HTML to Platform Accessibility draft doc. Sailesh Panchang
  • Re: Incorrect contact email id: Comments on HTML to Platform Accessibility draft doc. Steve Faulkner
• RE: Calculating accessible name - order Steve Faulkner
• RE: HTML5 Sentences, Paragraphs, and Phrases Con Badger
• Re: HTML5 Paragraphs, Sentences and Phrases Thomas A. Fine
  • Re: HTML5 Paragraphs, Sentences and Phrases Arthur Clifford
  • Re: HTML5 Paragraphs, Sentences and Phrases Thomas A. Fine
  • Re: HTML5 Paragraphs, Sentences and Phrases T.J. Crowder
• Adding language metadata on code elements Kevin Sweeney
  • Re: Adding language metadata on code elements Ian Hickson
• HTML5 link relationships: @rel='tag' Paul "Sparrow Hawk" Biron
• globalAlpha messing me up Jason H
  • Re: globalAlpha messing me up Ian Hickson
• Moving an iframe in the DOM John J Barton
  • Re: Moving an iframe in the DOM T.J. Crowder
  • Re: Moving an iframe in the DOM Simon Pieters
  • Re: Moving an iframe in the DOM John J Barton
  • Re: Moving an iframe in the DOM Ian Hickson
• Proposal for new tag to mark sentences. Thomas A. Fine
• HTML Tag of INPUT ChihJenWu
  • Re: HTML Tag of INPUT David Clarke
  • Re: HTML Tag of INPUT Chris Baker
• Update Cabdulqadir salad
• appcache: possibility to ignore url parameters / url parameter values Fenn Christopher
• title attribute Elisabeth Robson
• html5, details node, events Michael A. Peters
  • Re: html5, details node, events Jeffrey Way
  • Re: html5, details node, events T.J. Crowder
  • Re: html5, details node, events Michael A. Peters
  • Re: html5, details node, events Michael[tm] Smith
• Since when is an affadavit of implementation part of the Last Call Process shelleyp
• how to read a spec Elisabeth Robson
  • Re: how to read a spec Anne van Kesteren
• Follow-up about PUT and DELETE in form methods Thibault Jouannic
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods thibault
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Arthur Clifford
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Mirko Gustony
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods mike amundsen
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
  • Re: Follow-up about PUT and DELETE in form methods mike amundsen
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Cameron Heavon-Jones
  • Re: Follow-up about PUT and DELETE in form methods Julian Reschke
• Tabular Data / Processing model: column group Christian Roth
• Dublin Core/GRDDL Gannon Dick
• Security problem with the specification keygen Francisco Corella
  • Re: Security problem with the specification keygen Anders Rundgren
  • Re: Security problem with the specification keygen Francisco Corella
• Image width specification in html5 David Swindlehurst
  • Re: Image width specification in html5 Michael[tm] Smith
  • Re: Image width specification in html5 Arthur Clifford
  • Re: Image width specification in html5 Michael[tm] Smith
  • Re: Image width specification in html5 Arthur Clifford
  • Re: Image width specification in html5 David Swindlehurst
  • Re: Image width specification in html5 Jukka K. Korpela
  • Re: Image width specification in html5 Simon Pieters
  • Re: Image width specification in html5 Jukka K. Korpela

• Earlier messages
• Later messages