Claas Augner

> @caugner can you check [3d8a8bf](https://github.com/mdn/content/commit/3d8a8bf7a9ab597f101c774079d9bb235b58646b) to let me know if it looks okay? @bsmth Thank you for taking over, looking good to me on the preview! 🙌

This looks like a limitation of the css-examples, see: https://mdn.github.io/css-examples/learn/tasks/selectors/combinators.html

@salmenf Thanks for reporting. As you mention, the MDN page correctly reproduces the syntax from the CSS specification, so there is no issue on our side that needs addressing and...

@amyblias Who might be able to review this PR?

Unfortunately, the mattermost apt list seems to have an invalid origin: 🤔 ```console $ grep -P "Origin|Suite" /var/lib/apt/lists/deb.packages.mattermost.com_dists_focal_InRelease 1 ↵ Origin: . focal Suite: focal $ grep -P "Origin|Suite" /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_focal-security_InRelease...

Maybe this could be fixed by telling Aptly to set the Origin field to "mattermost" or similar here: https://github.com/mattermost/mattermost-omnibus/blob/7ec7fe269b851a0bfb584941e92acf1f468be239/scripts/sync-and-publish#L36-L37

Here are the origins that other repos use: ``` $ grep -hR Origin: /var/lib/apt/lists/ | sort -u 130 ↵ Origin: apt.postgresql.org Origin: . focal Origin: nginx Origin: Ubuntu ``` **edit**:...

FWIW If Mattermost's Origin field were set to "Mattermost" (to be consistent with "Ubuntu"), unattended upgrades could be configured as follows: ``` Unattended-Upgrade::Allowed-Origins { "Mattermost:${distro_codename}"; }; ```

See: https://github.com/mdn/browser-compat-data/pull/25789 This appears to not be a breaking change, because the requirement isn't reflected in the exported TypeScript definitions. We could merge `engine` and `engine_version` into an `engine: {...

See also: https://github.com/orgs/mdn/discussions/736