Closed
Bug 1817475
Opened 3 years ago
Closed 3 years ago
[wpt-sync] Sync PR 38570 - Add a test for sticky position with fractional offsets
Categories
(Core :: Layout: Positioned, task, P4)
Core
Layout: Positioned
Tracking
()
RESOLVED
FIXED
112 Branch
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 38570 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/38570
Details from upstream follow.
Philip Rogers <pdr@chromium.org> wrote:
Add a test for sticky position with fractional offsets
When a sticky positioned element has a fractional offset, a 1px gap
should not bleed through.Bug: 1136079
Change-Id: I37aaa399529d1c4bf82a33b33bb0e491ec8cfca3
Reviewed-on: https://chromium-review.googlesource.com/4262133
WPT-Export-Revision: 87c4f9a3281e12de9b17b228ba5810eba2a7700c
| Assignee | ||
Updated•3 years ago
|
Component: web-platform-tests → Layout: Positioned
Product: Testing → Core
| Assignee | ||
Comment 1•3 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=f1b2a0025ef5e111dc69641312bcfe2ac1744f31
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d2a040d1d0f9
[wpt PR 38570] - Add a test for sticky position with fractional offsets, a=testonly
| Assignee | ||
Comment 3•3 years ago
|
||
Test result changes from PR not available.
| Assignee | ||
Comment 4•3 years ago
|
||
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/466debdba2a5
[wpt PR 38570] - Add a test for sticky position with fractional offsets, a=testonly
Comment 6•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
| Assignee | ||
Comment 7•3 years ago
|
||
Test result changes from PR not available.
You need to log in
before you can comment on or make changes to this bug.
Description
•