Closed Bug 1624665 Opened 4 months ago Closed 4 months ago

[wpt-sync] Sync PR 22422 - Apply adjustments for 'text-anchor' after 'textLength' for <textPath>

Categories

(Core :: SVG, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Fredrik Söderqvist <fs@opera.com> wrote:

Apply adjustments for 'text-anchor' after 'textLength' for <textPath>

When computing the position on the path for 'text-anchor' adjustments,
any potential adjustments performed for 'textLength' needs to be
considered. Previously the adjustment was computed as part of the
summation of the chunk lengths.

Bug: 603995
Change-Id: I579688e9ecf33a17898ecf228de6d44337455ed8
Reviewed-on: https://chromium-review.googlesource.com/2116236
WPT-Export-Revision: 09a025b58b1535d660a984d3795d8887210760e8

Component: web-platform-tests → SVG
Product: Testing → Core

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/svg/text/scripted/textpath-textlength-text-anchor-001.tentative.svg
'textLength' on <textPath> with 'text-anchor' adjustments: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cbb5a8047c2d
[wpt PR 22422] - Apply adjustments for 'text-anchor' after 'textLength' for <textPath>, a=testonly
https://hg.mozilla.org/integration/autoland/rev/b5e3d055fac8
[wpt PR 22422] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in before you can comment on or make changes to this bug.