Kasper Isager Dalsgarð

For now, we'll handle the case of `` elements in SIA-R40 directly (#678), but on second thought I'll not consider that a solution to this issue. Seeing how Firefox is...

As discussed at check-in, the easiest solution to this seems to be to drop illegal declarations from `rule.style` if `part` contains a `:visited` selector here: https://github.com/Siteimprove/alfa/blob/578fb689cf50b783b46e3412e0b7c5906bfdb77f/packages/alfa-cascade/src/selector-map.ts#L220

Chromium uses entirely separate property definitions for style properties that are allowed in `:visited` declarations: https://source.chromium.org/chromium/chromium/src/+/master:third_party/blink/renderer/core/css/properties/css_property.h;l=120-124;drc=9680e17185f4d0a48a7047d0070ef26d1df282d6

Yep, and properties that are allowed to depend on `:visited` are handled here: https://github.com/servo/servo/blob/b196bfeeeb90e87769700b52202e898da999f8da/components/style/properties/properties.mako.rs#L1309-L1334

@mafintosh This is ready for review.

@mafintosh I'm at a bit of an impasse with regards to `EventEmitter`. It's simple enough to shim with the http://npmjs.com/events module ~but that module cannot be installed without forcing every...

I can contribute the first use case: The thing I'm currently working on is a browser first, Node.js second type of thing that uses `streamx`. Being browser first, adding `events`...

> actually zero overhead right, cause node should just skip it? That's absolutely true, I missed that! To actually import the `events` module in Node.js, and not the builtin module,...

For reference, the following works for GitHub Packages: https://github.com/Siteimprove/alfa/blob/c448d93e030b0f6b55433dec5bc667d874befd87/.github/workflows/release.yml#L15-L18

I'd love to see something like this as well!