Closed
Bug 1497327
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 13376 - Make Element#innerText to collapse white spaces after <br>
Categories
(Core :: DOM: Core & HTML, enhancement, P4)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 13376 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/13376
Details from upstream follow.
Yoshifumi Inoue <yosin@chromium.org> wrote:
> Make Element#innerText to collapse white spaces after <br>
>
> This patch makes Element#innerText to collapse white space after \<br> to avoid
> emitting extra space for improving interop.
>
> Bug: 892491
> Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
> Change-Id: I8dd429a8af6ecd2e6d5195d6a6ec7b0214c6345c
> Reviewed-on: https://chromium-review.googlesource.com/c/1263638
> Reviewed-by: Yoichi Osato \<yoichio@chromium.org>
> Commit-Queue: Yoshifumi Inoue \<yosin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#597004}
>
| Assignee | ||
Updated•7 years ago
|
Component: web-platform-tests → DOM
Product: Testing → Core
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=b8212930cee3f7239938de49f8b3cebef6dfb54b
| Assignee | ||
Comment 3•7 years ago
|
||
Ran 1 tests and 215 subtests
OK : 1
PASS : 214
FAIL : 1
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/06f46420815f
[wpt PR 13376] - Make Element#innerText to collapse white spaces after <br>, a=testonly
Comment 5•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•