[Bug 13098] Clarify whether <wbr> has the same effect as the zero-width space character

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13098

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |NEEDSINFO

--- Comment #13 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-06 21:08:03 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:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Additional Information Needed
Change Description: no spec change
Rationale: This bug, as originally filed and then amended, postulated that
<wbr> and zwsp are equivalent, and asked for that to be clarified.  However,
per the current spec, they are not equivalent.  Making them equivalent is what
bug 9097 requests, and I've left that open for Hixie to review the evidence you
provided.

Could you please explain what this bug is supposed to do in addition to bug
9097?  If 9097 is fixed, <wbr> and zwsp will be defined as equivalent as
requested.  If 9097 is wontfixed, this bug is invalid because <wbr> and zwsp
are defined to *not* be equivalent: e.g., as now, <wbr> will be defined to
create a break even in <pre>.  So I don't get what this bug is asking for now.

-- 
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 21:08:10 UTC