{text-align:justify} bug - wrong changes space between words or characters

[Pavel Marakhovski]

Two same element with css {text-align:justify}:
<div>Lorem ipsum dolor sit amet, consectetur adipiscing</div>
<div>Lorem ipsum dolor <span>sit amet, consectetur</span> adipiscing</div>
But result wrong difference in space between words or characters.
In firefox everything ok.

fiddle - http://jsfiddle.net/JooobyPM/sp0dkbme/

[Pavel Marakhovski]

http://stackoverflow.com/questions/25980785/webkit-and-blink-rendering-bug-text-alignjustify

[Alexey Proskuryakov]

This still happens with trunk, so subpixel positioning doesn't appear to have had an effect here.

[zalan]

apparently when the leading whitespace gets included to the <span>, text positioning is all fine.
Lorem ipsum dolor<span> sit amet, consectetur</span> adipiscing
instead of
Lorem ipsum dolor <span>sit amet, consectetur</span> adipiscing

[Pavel Marakhovski]

(In reply to comment #3)
> apparently when the leading whitespace gets included to the <span>, text positioning is all fine.
> Lorem ipsum dolor<span> sit amet, consectetur</span> adipiscing
> instead of
> Lorem ipsum dolor <span>sit amet, consectetur</span> adipiscing

Text position is fine only for specific width, but if change width text position is not fine:
http://jsfiddle.net/JooobyPM/aqLkja5s/

[Myles C. Maxfield]

See https://bugs.webkit.org/show_bug.cgi?id=137327

[Pavel Marakhovski]

In r174259 bug resolved.

[Alexey Proskuryakov]

So is this a duplicate of bug 137327?

[Pavel Marakhovski]

(In reply to comment #7)
> So is this a duplicate of bug 137327?

Bug 137327 was reported - [2014-10-01 17:27 PST by Myles C. Maxfield]
Bug 137016 (this one) was reported - [2014-09-22 17:32 PST by Pavel Marakhovski]

[Alexey Proskuryakov]

It is indeed the case that we prefer to dupe to older bug. There are exceptions to the rule:

- when a newer bug is already fixed, or has significant discussion that would be difficult to transfer to another bug;

- or when the older bug is difficult to read or understand for some reason, so keeping it open would only delay making a fix.

Bug 137327 is already fixed. My question was essentially whether it fully resolves the issue reported here, or if there is anything left hidden under the carpet.

[Pavel Marakhovski]

(In reply to comment #9)
> It is indeed the case that we prefer to dupe to older bug. There are exceptions to the rule:
> 
> - when a newer bug is already fixed, or has significant discussion that would be difficult to transfer to another bug;
> 
> - or when the older bug is difficult to read or understand for some reason, so keeping it open would only delay making a fix.
> 
> Bug 137327 is already fixed. My question was essentially whether it fully resolves the issue reported here, or if there is anything left hidden under the carpet.

This two bugs is cause and effect. I ran my examples on webkit r174259-r174324 (MacOS) and it looks like problem was solved. So I think this bug was fixed.

[Alexey Proskuryakov]

What is the reason for you to insist on marking this bug FIXED? We use this resolution for bugs that have a fix in them. Bugs with a fix are special, because the fix can break other things, the fix can be rolled out, etc.

[Pavel Marakhovski]

(In reply to comment #11)
> What is the reason for you to insist on marking this bug FIXED? We use this resolution for bugs that have a fix in them. Bugs with a fix are special, because the fix can break other things, the fix can be rolled out, etc.

Seems it my mistake. If I understand right I can mark this bug DUPLICATE.  
In my humble opinion fixe on the bug 137327 fully resolves the issue reported here, and nothing left hidden under the carpet.

*** This bug has been marked as a duplicate of bug 137327 ***