W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 9350] Make <wbr> element conforming

From: <bugzilla@jessica.w3.org>
Date: Wed, 06 Jul 2011 20:01:33 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QeYHt-0000qt-AI@jessica.w3.org>

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #16 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-06 20:01:32 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:


Status: Partially Accepted
Change Description: see comment 4
Rationale: Re-resolving as fixed.

* There is existing browser support of some form in all browsers, which means
we have to spec it and implementers have to implement it, unless you can get
major implementers to drop support.

* Once a feature has to be implemented anyway, the threshold for making it
valid is low.  If this were a new feature request, it would be rejected, but we
prefer to make existing features valid unless there are relatively good reasons
against.  That minimizes useless validator noise and encourages authors to use
validators more.

* There are some use-cases for <wbr>.  They aren't very strong, but given that
we're stuck with it anyway, they're strong enough to make it valid.

* The fact that existing browsers implement <wbr> inconsistently and authors
are confused about it is not a strong argument against making it valid.  Both
of those things are true about many preexisting web features.  Either we have
to drop support entirely, or specify it and get browsers to converge,
regardless of validity.

I recommend that you do not continue to reopen bugs on this issue.  You have
two viable options:

1) File bugs against browsers and try to get them to agree to drop <wbr>
support entirely.  If implementers are willing to drop support, we can remove
the element entirely, which is a win for simplicity of the platform.  I suspect
it's widely enough used that you won't be able to convince them, though.

2) Follow the instructions in the boilerplate at the top of this comment to
escalate to an issue: "add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue".

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 20:01:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:55 UTC