- From: <bugzilla@jessica.w3.org>
- Date: Wed, 06 Jul 2011 01:06:48 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9350 --- Comment #14 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-07-06 01:06:46 UTC --- (In reply to comment #11) > (In reply to comment #10) > > Reopening an already-fixed bug a year later is probably not the best way to > > have the matter reconsidered. > > What is the best way? I am ready to author a Change Proposal. > > Because <wbr> seems like one of the most pointless and unjustified additions > to HTML5 ever. When you justified <wbr>, you pointed to Webkit's idiosyncratic implementation of it, and portrayed Webkit's interpetations as more or less the "standard" way that browser implements it. E.g you described <wbr> as breaking with CSS and gave the impression that it was *necessary* to break with CSS. Well, my test page shows that Webkit's implementation differs from everyone elses. In addition, Webkit is only surpassed by Konqueror when it comes to word boundaries bugs. (E.g. the fact that Webkit sees as inline <span/> as a word boundary.) Even the Editor showed himself to be not 100% at ease with the "fixed" solution - why else the he add comment 7, after the bug was "fixed".? Since this bug was fixed by pointing to Webkit's behaviour, the entire element IMO needs to be reevaluated if we reach the shared conclusion that Webkit's behaviour is particular to that browser. For the record: It would be much more easy to accept a *sane* interpretation of <wbr> - e.g. the one found in Firefox. which as far as I can see, *fully* aligns <wbr> with ZERO WIDTH SPACE. -- 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 Wednesday, 6 July 2011 01:06:54 UTC