1811161 - `Document.execCommand("forecolor")` should use normalized value at setting HTML attribute value

Status: RESOLVED FIXED

(Core :: DOM: Editor, defect, P3)

Description

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Chrome sets corresponding attribute value to #[0-9a-f]{6} even if color name is specified. However, our style editor sets given color value as-is. We should align the behavior to Chrome.

Comment 2

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Attachment: Bug 1811161 - Make the style editor sets `color` attribute value of `<font>` to normalized color value r=m_kato!

Currently, our editor sets color attribute of <font> to given value as-is.
However, the other browsers normalize it to #[0-9a-z]{6} before setting the
value, and some WTP expects the behavior. Therefore, we need to follow it for
avoiding meaningless failures.

According to WPT, the parameter can be "transparent" even without
styleWithCSS. Additionally, CSS color values are also allowed if
styleWithCSS is true. Therefore, this patch includes some fixes for them
too to avoid new failures.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0659120fb8f2
Make the style editor sets `color` attribute value of `<font>` to normalized color value r=m_kato

Comment 4

[Web Platform Test Sync Bot (Matrix: #interop:mozilla.org)]

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/38193 for changes under testing/web-platform/tests

Comment 5

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/0659120fb8f2

Comment 6

[Web Platform Test Sync Bot (Matrix: #interop:mozilla.org)]

Upstream PR merged by moz-wptsync-bot