[CSS] Ship COLRv1 color-font support

[hamishwillee]

Acceptance Criteria

• The listed features are documented sufficiently on MDN
• BCD is updated
• Interactive example and data repos are updated if appropriate
• The content has been reviewed as needed

For folks helping with Firefox related documentation

• Set bugs to dev-doc-complete
• Add entry to Firefox release notes if feature is enabled in release
• Add entry to Firefox experimental features page if feature is not yet enabled in release

Features to document

This enables the COLRv1 color-font support that was added in FF105 behind the prefix gfx.font_rendering.colr_v1.enabled - see #20106.

Need to:

• Add FF107 release note and remove from experimental features
• Update BCD to remove the flag and make this as no longer experimental
• Perhaps update https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face with an example.

Related Gecko bugs

https://bugzilla.mozilla.org/show_bug.cgi?id=1791558

Other

• Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
• Check if Glossary updates are required for the feature you're documenting - whether an existing term needs to be updated or a new term should be added.
• Check if BCD update means that content pages need to have experimental markup removed or deprecated markup added (front matter tags and macros).

[bsmth]

Note that there might be nice overlap with #20917 :

@supports font-tech(color-COLRv1) {
  font-family: "my cool colrv1 font";
}

[Rumyra]

I think there's overlap with the following bugs as well:

https://bugzilla.mozilla.org/show_bug.cgi?id=1794277
https://bugzilla.mozilla.org/show_bug.cgi?id=1794091

I can split these up but it might be worthwhile for who picks this up to tackle altogether(?)

[hamishwillee]

Certainly the first one could be combined IMO. Would be good to cross link the bugs when this is decided, so you can always find out what was done in our team from the bugzilla end.

[Rumyra]

Would be good to cross link the bugs when this is decided, so you can always find out what was done in our team from the bugzilla end.

As in bugzilla links on bugzilla?

[hamishwillee]

As in bugzilla links on bugzilla?

Yes. From a project management point of view you can save yourself a lot of time if it is easy to work out the corresponding issue(s) from github or bugzilla. The easiest way to do that is to add a note in both stating the "opposite" issue.

[Rumyra]

https://bugzilla.mozilla.org/show_bug.cgi?id=1794091

• MDN page needed
• BCD updates
• Rel note
• dev-doc-complete

https://bugzilla.mozilla.org/show_bug.cgi?id=1794277

• Check https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face and other font docs
• BCD updates
• Rel note
• dev-doc-complete

https://bugzilla.mozilla.org/show_bug.cgi?id=1791558

• As this is a font format a page isn't needed, but most likely related to font-palette - check other docs for font format copy
• Rel note
• dev-doc-complete

Also making a note that a guide for these new font shinanigans is probably needed, but outside the scope of this issue (something for the Fonts Level 4 review @dipikabh )

[dletorey]

Right I believe that I have now finished this, it ended up being way bigger than I first thought.
Although it has meant that I have learnt how to do many parts of creating content in MDN.
Just creating a PR for it all.

[hamishwillee]

It's always way bigger than I think :-).

[hamishwillee]

PS When something is done, you can move it to Done in https://github.com/orgs/mdn/projects/12/views/6