Closed
Bug 1505266
Opened 6 years ago
Closed 6 years ago
[wpt-sync] Sync PR 13962 - [LayoutNG] Fix vertical-align: text-top in quirks mode
Categories
(Core :: Layout, enhancement, P4)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla65
Tracking | Status | |
---|---|---|
firefox65 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 13962 into mozilla-central (this bug is closed when the sync is complete). PR: https://github.com/web-platform-tests/wpt/pull/13962 Details from upstream follow. Koji Ishii <kojii@chromium.org> wrote: > [LayoutNG] Fix vertical-align: text-top in quirks mode > > When in quirks mode and there are no text siblings; e.g.: > \<div>\<img>\<span>text\</span>\</div> > and 'vertical-align: text-top' applied to \<img> hits > DCHECK failure and results in incorrect position. > > The test ensures that results are the same with the standard > mode. > > Bug: 901123 > Change-Id: I30564c66d5847f09caf3672ba3d456c0eb798d3e > Reviewed-on: https://chromium-review.googlesource.com/1320529 > WPT-Export-Revision: e22c09ab5145d7a333d792eb35174f9ba31e3d7d
Assignee | ||
Updated•6 years ago
|
Component: web-platform-tests → Layout
Product: Testing → Core
Assignee | ||
Comment 1•6 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=636f9a4f0b9314cfa9eefa86b0cca3007f8181dc
Assignee | ||
Comment 2•6 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=778974eff7f9b5deb6e8bc363b9c1efabf644bcc
Assignee | ||
Comment 3•6 years ago
|
||
Ran 1 tests PASS : 1
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/36a98062a94b [wpt PR 13962] - [LayoutNG] Fix vertical-align: text-top in quirks mode, a=testonly
Comment 5•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/36a98062a94b
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in
before you can comment on or make changes to this bug.
Description
•