Opened 3 years ago
Closed 3 years ago
#17258 closed bug (fixed)
WebKit 613.1.1 - scrambled fonts on some pages
| Reported by: | vidrep | Owned by: | pulkomandy |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta4 |
| Component: | Kits/Web Kit | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
hrev55402 x86_64
WebKit 613.1.1
Some pages display scrambled fonts. WebKit 612.1.21 not affected
Screenshot attached
Attachments (1)
Change History (5)
by , 3 years ago
| Attachment: | screenshot1.png added |
|---|
comment:1 by , 3 years ago
comment:3 by , 3 years ago
| Component: | Applications/WebPositive → Kits/Web Kit |
|---|---|
| Version: | R1/beta3 → R1/Development |
One possible fix: https://github.com/haiku/haikuwebkit/pull/6
comment:4 by , 3 years ago
| Milestone: | Unscheduled → R1/beta4 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
The fix is merged, this will be part of the next webkit release.
Note:
See TracTickets
for help on using tickets.
B2IA messages have Ctrl-C characters in them.
I can't test it now, but this is probably due to an upstream change to make some control characters visible. The implementation changes them to the .notdef glyph, which is code 0. In our port that transforms into a NULL character that is not added to the string and we get characters and advances out of sync.
We could revert that or change the 0 (either there or in FontHaiku) for the replacement character, another non-character (that hopefully won't have a glyph and so come as .notdef), the white square (as was proposed when we had a similar problem before) or whatever. The same should be done wherever we return the advances.