Closed Bug 1774859 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 34485 - HTMLQuoteElement quote delimiters should be based on lang of parent

Categories

(Core :: Layout: Generated Content, Lists, and Counters, task, P4)

task

Tracking

()

RESOLVED FIXED
104 Branch
Tracking Status
firefox104 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

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

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

Di Zhang <dizhangg@chromium.org> wrote:

HTMLQuoteElement quote delimiters should be based on lang of parent

Following the resolution of WHATWG HTML standard [1] and
existing CSS issue [2], it has been decided that the
auto (default) lang for \<q> element should be based on the parent
language.

This CL makes sure to skip reading the lang attribute for \<q>.
Instead, its locale is calculated in
CollectExtraStyleForPresentationAttribute(), using the parent's locale.

[1] https://github.com/whatwg/html/issues/3636
[2] https://github.com/w3c/csswg-drafts/issues/5478

Change-Id: Ief17dd1e7f5a40112899ce898fa672a6fef6e834
Bug: 1290851
Bug: 753671

Reviewed-on: https://chromium-review.googlesource.com/3704149
WPT-Export-Revision: bda1ca4c82d3ed30d9c9653a8be4426071c43373

Component: web-platform-tests → Layout: Generated Content, Lists, and Counters
Product: Testing → Core

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/199f2c937da9 [wpt PR 34485] - HTMLQuoteElement quote delimiters should be based on lang of parent, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
You need to log in before you can comment on or make changes to this bug.