Summary: | REGRESSION (r78846): Text misaligned vertically within table cell with valign="top" attribute and <sup> tags | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | David Kilzer (:ddkilzer) <ddkilzer> | ||||||||||
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||||||||
Status: | RESOLVED CONFIGURATION CHANGED | ||||||||||||
Severity: | Normal | CC: | ahmad.saleem792, ap, bfulgham, flangeway, hyatt, mitz, rluna, rniwa, simon.fraser, tom239, zalan | ||||||||||
Priority: | P2 | Keywords: | HasReduction, InRadar, Regression | ||||||||||
Version: | 528+ (Nightly build) | ||||||||||||
Hardware: | All | ||||||||||||
OS: | All | ||||||||||||
Bug Depends on: | 54244 | ||||||||||||
Bug Blocks: | |||||||||||||
Attachments: |
|
Description
David Kilzer (:ddkilzer)
2011-09-14 12:05:46 PDT
Created attachment 107367 [details]
Test case
The changes to InlineFlowBox::adjustMaxAscentAndDescent() (consulting verticalAlign() instead of logicalTop()) are possiblly at fault here. Created attachment 107368 [details]
Expected results
Created attachment 107369 [details]
Actual results
This is still unfixed two years later. It was recently reported at https://code.google.com/p/chromium/issues/detail?id=135657 and I've added a comment there linking to this page. Created attachment 214973 [details]
screenshot attached
There seem to be two bugs present:
- the incorrect baseline rendering of the majority of fonts in a table td with vertically-aligned bold or italic content;
- the amplification of such baseline errors, for any font, when superscript tags are used.
The bug is not apparent in Internet Explorer, Opera or Firefox, but does occur in Safari 5.1. The bug is partially present in Safari 6 on Mac and Chrome 30 on Unix. The bug appears to be dependent on operating system.
I attach a screenshot.
just adding a note that I run into this on occasion as i do a lot of html emails using table-based layouts for use in exact target, campaigner, etc. This bug now seems to be fully resolved with Chrome 46. See https://code.google.com/p/chromium/issues/detail?id=135657 I am unable to reproduce this bug in Safari 15.6.1 and Safari Technology Preview 152 using attached test case and it shows similar behavior as "EXPECTED RESULT" and matching both Chrome Canary 107 and Firefox Nightly 106. It seems to be something fixed along the way. I am going to mark this as "RESOLVED CONFIGURATION CHANGED". Please reopen with updated test case in case if it is still present. Thanks! |