Closed
Bug 253144
Opened 20 years ago
Closed 16 years ago
Word spacing is not applied to zero width spaces
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: mozilla, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7) Gecko/20040724 Firefox/0.9.1+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7) Gecko/20040724 Firefox/0.9.1+ CSS word-spacing is not applied to zero width spaces, despite them being treated as a whitespace character (bug 37862). See attachment 154392 [details] at bug 253143 comment 1. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Comment 1•20 years ago
|
||
Note bug 164700
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Works for me back to Fx 2.0
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Comment 4•16 years ago
|
||
I don't see that this is working in the testcases in bug 253143. Do you have a testcase that shows that it is working?
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 5•16 years ago
|
||
That said, I believe this is actually invalid: the interaction between word-spacing and zero-width spaces isn't defined in CSS2, but CSS3 says (http://www.w3.org/TR/css3-text/#word-spacing): |If there are no word-separator characters, or if the word-separating character |has a zero advance width (such as the zero width space U+200B) then the user |agent must not create an additional spacing between words.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → INVALID
I'm sorry, I had both bugs open and they got me confused. Actually I was about to close bug 253143, because according to CSS 2.1, it is right to add letter-spacing to U+200B. CSS 2.1 §16.4 (http://www.w3.org/TR/CSS21/text.html#propdef-letter-spacing): > <length> > This value indicates inter-character space *in addition* to the default > space between characters. Since were at at anyway, what do you think? (In reply to comment #5) > That said, I believe this is actually invalid: the interaction between > word-spacing and zero-width spaces isn't defined in CSS2, but CSS3 says > (http://www.w3.org/TR/css3-text/#word-spacing): That would've been my next step, sorry for getting confused. I'll take care.
Comment 7•16 years ago
|
||
(In reply to comment #6) > Actually I was about to close bug 253143, because according to CSS 2.1, it is > right to add letter-spacing to U+200B. > > CSS 2.1 §16.4 (http://www.w3.org/TR/CSS21/text.html#propdef-letter-spacing): > > <length> > > This value indicates inter-character space *in addition* to the default > > space between characters. > > Since were at at anyway, what do you think? No, I think that letter-spacing should not apply to invisible characters, and we should fix bug 253143. See the last few comments in bug 464148.
Comment 8•16 years ago
|
||
Or rather bug 464168
(In reply to comment #8) > Or rather bug 464168 Right. I get your point, thanks. Ok, no further need for spamming.
You need to log in
before you can comment on or make changes to this bug.
Description
•