Use the value attribute for color update if dirty value flag is false

[saschanaz]

Fixes #12057

• At least two implementers are interested (and none opposed):
  • WebKit (already implemented)
  • Gecko
• Tests are written and can be reviewed and commented upon at:
  • WPT already expects this
• Implementation bugs are filed:
  • Chromium: (the attributes are not implemented there yet)
  • Gecko: Will be part of https://bugzilla.mozilla.org/show_bug.cgi?id=1919718
  • WebKit: N/A
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): N/A
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): N/A
• Corresponding HTML AAM & ARIA in HTML issues & PRs: N/A
• MDN issue is filed: N/A?
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

[saschanaz]

Do I now need to do something to trigger preview, or the bot is misbehaving? Hmm.

(#12069 isn't getting preview either, so not just this one)

[annevk]

The wording of that step feels a tad ambiguous. Perhaps it's better to make it two steps?

[saschanaz]

The wording of that step feels a tad ambiguous. Perhaps it's better to make it two steps?

I made it two paragraphs in one step, as it seems it's sufficiently common in HTML to do so. There are a few instances of separate-step usage too, so either way is okay for me but I thought this could feel a bit more natural.

[annevk]

It seems this fails on CI. Modern style doesn't do initialization of a variable twice so that needs to be done differently.

[saschanaz]

Modern style doesn't do initialization of a variable twice so that needs to be done differently.

You mean merge it back?