|
Lines 1-3
a/Source/WebCore/ChangeLog_sec1
|
|
|
1 |
2016-04-05 Myles C. Maxfield <mmaxfield@apple.com> |
| 2 |
|
| 3 |
REGRESSION (r188591): thingiverse.com direct messaging UI is not rendered properly |
| 4 |
https://bugs.webkit.org/show_bug.cgi?id=156241 |
| 5 |
<rdar://problem/25262213> |
| 6 |
|
| 7 |
Reviewed by NOBODY (OOPS!). |
| 8 |
|
| 9 |
text-rendering: optimizeLegibility enables optical sizing. When using an optical |
| 10 |
size of 0, CoreText actually uses a size of 12. In this situation, a space character |
| 11 |
will have a non-zero advance, causing it to take some space in inline layout. This |
| 12 |
was causing an unexpected line-wrap. |
| 13 |
|
| 14 |
Other browsers don't turn on optical sizing when text-rendering: optimizeLegibility |
| 15 |
is specified, so they don't have this problem. |
| 16 |
|
| 17 |
The solution is to detect a zero-sized font, and force the advances to 0. |
| 18 |
|
| 19 |
Test: fast/text/zero-sized-fonts.html |
| 20 |
|
| 21 |
* platform/graphics/FontCascade.cpp: |
| 22 |
(WebCore::FontCascade::width): |
| 23 |
* platform/graphics/WidthIterator.cpp: |
| 24 |
(WebCore::WidthIterator::advanceInternal): |
| 25 |
* platform/graphics/cocoa/FontCacheCoreText.cpp: |
| 26 |
(WebCore::preparePlatformFont): |
| 27 |
* platform/graphics/mac/ComplexTextController.cpp: |
| 28 |
(WebCore::ComplexTextController::adjustGlyphsAndAdvances): |
| 29 |
|
| 1 |
2016-04-04 Dean Jackson <dino@apple.com> |
30 |
2016-04-04 Dean Jackson <dino@apple.com> |
| 2 |
|
31 |
|
| 3 |
Add color-gamut media query support |
32 |
Add color-gamut media query support |