- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Jun 2011 17:36:02 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13098 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xn--mlform-iua@xn--mlform-i | |ua.no --- Comment #2 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-06-30 17:36:02 UTC --- (In reply to comment #1) HTML5's current problem is that there is that confusion exists in the wild (see the links I mentioned above) and that no account is made of the soft hyphen character's role in hyphenation. Othewise, you are right. However, similar to how it often is of no importance to the author whether a line break inside a <pre> element is made with a <br> or with the line feed character, it does for practical purposes usually not matter whether <wbr> or the soft hypen character is used. > should result in a HTMLElement in the DOM, not a text node as > when use ­ or the actual unicode character. You make it seem as if ­ is represented in the DOM differently from the directly typed soft hyphen character. However, when I check with Live DOM Viewer (or a built in DOM inspector of the browser) , then both ­ ­ as well as the directly typed character each seem to result the same kind of text node with: a text node containing an invisible (and even hard to select!) soft hyphen character. http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1049 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 30 June 2011 17:36:14 UTC