Closed Bug 1477885 Opened 6 years ago Closed 6 years ago

[wpt-sync] Sync PR 12152 - [css-logical] Replace uses of webkit-prefixed logical properties with standard ones in /third_party/WebKit/LayoutTests

Categories

(Core :: CSS Parsing and Computation, enhancement, P4)

enhancement

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 12152 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/12152
Details from upstream follow.

Oriol Brufau <obrufau@igalia.com> wrote:
>  [css-logical] Replace uses of webkit-prefixed logical properties with standard ones in /third_party/WebKit/LayoutTests
>  
>  Bug 850000 added standard logical properties and aliased prefixed ones
>  to them. The prefixed properties are still used in various places, but
>  the standard ones should be used instead. This patch replaces all the
>  uses in /third_party/WebKit/LayoutTests, except in one test to ensure
>  that prefixed properties continue working:
>  fast/writing-mode/orthogonal-inline-block.html
>  
>  Spec: https://drafts.csswg.org/css-logical/#box
>  
>  BUG=862141
>  
>  Change-Id: I3090713fc6fbe507a19724cca4f6ca69bcaf5eb9
>  Reviewed-on: https://chromium-review.googlesource.com/1147523
>  WPT-Export-Revision: 1e56ec90ff1e34fc911dc9f0f419019dcf7564d2
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Ran 1 tests and 120 subtests
OK     : 1
PASS   : 108
FAIL   : 12
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/269d888d50ad
[wpt PR 12152] - [css-logical] Replace uses of webkit-prefixed logical properties with standard ones in /third_party/WebKit/LayoutTests, a=testonly
https://hg.mozilla.org/mozilla-central/rev/269d888d50ad
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.