28825 2015-06-18 17:44:54 +0000 Should empty-element tags include a space before forward slash e.g. "<br />"? 2015-06-18 18:02:57 +0000 1 1 1 Unclassified HTML WG CR HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified PC Windows NT NEW P2 enhancement --- 1 johnny_bentley dave.null johnny_bentley public-html-bugzilla oldest_to_newest 121216 0 johnny_bentley 2015-06-18 17:44:54 +0000 "Polyglot Markup: A robust profile of the HTML5 vocabulary", W3C Editor's Draft 07 May 2014, 4.6.1 Void elements, http://dev.w3.org/html5/html-polyglot/html-polyglot.html#empty-elements This current specification for using empty-element tags exemplifies this without a space before the forward slash. That is, we currently have examples like "<br/>". However, in the past the recommendation (in the web community at large) was to include a space before the forward slash, as in "<br />", for compatibility reasons. I'd recommend including a note, or otherwise amending the document, to clarify the use of spaces before the forward slash (as in "<br />"). I'm not clear on whether any of the current crop of browsers still requires a usage like "<br />". I suggest a note to the effect of one of the following be included (depending on the state of affairs) ... A) "Both uses, as in '<br/>' or '<br />', are permitted. While a use like '<br />' was formerly required for compatibility, this is no longer the case". B) "Use something like '<br />', not '<br/>', for compatibility reasons." C) ? 121217 1 eliotgra 2015-06-18 17:50:14 +0000 I'm afraid I am no longer editing this spec. 121218 2 johnny_bentley 2015-06-18 18:02:57 +0000 That's a shame, so far it's been a well written document. Would the following therefore be the right course of action for you to take: * Take your name off the document "Polyglot Markup: A robust profile of the HTML5 vocabulary" as a current editor (and list yourself as a former editor); and * Contact Leif H. Silli to see if they would be happy to include their email here at bugzilla, against the "CR HTML/XHTML Compatibility Authoring Guide" (Polyglot Markup: A robust profile of the HTML5 vocabulary) entries. * Ensure Leif is aware of this "bug" (the first "bug" for the document?). ?