Devon Govett

If anyone is still seeing this, please test `@parcel/watcher` v2.4.2-alpha.0, which includes https://github.com/parcel-bundler/watcher/pull/177 to fix some use after free issues and see if it helps.

I think we probably will not support that syntax, but perhaps via a different one. The reason is that the CSS spec requires an `` keyword there, not a selector....

Closing now that https://github.com/adobe/react-spectrum/pull/8327 is merged.

I'm not sure how we'd detect this automatically. We just look to see if the popover element has a transition applied using [element.getAnimations()](https://developer.mozilla.org/en-US/docs/Web/API/Element/getAnimations), but this would require traversing the DOM...

Ah actually looks like there is an option for this: `element.getAnimations({subtree: true})`.

Going to close this. There's not a good way to determine which animations on elements inside a popover are related to entry or exit animations and which one are independent....

Wouldn't this result in there being multiple highlighted items at once? e.g. one that you focused with the keyboard and one that you hovered over. By focusing the item on...

I still feel like the better option would be to add a prop to prevent selecting the focused item on Tab, instead of tying this to hover only. As it...

This already works? [playground](https://lightningcss.dev/playground/index.html#%7B%22minify%22%3Afalse%2C%22customMedia%22%3Atrue%2C%22cssModules%22%3Afalse%2C%22analyzeDependencies%22%3Afalse%2C%22targets%22%3A%7B%22chrome%22%3A6225920%7D%2C%22include%22%3A0%2C%22exclude%22%3A0%2C%22source%22%3A%22%40media%20(min-width%3A%20576px)%20%7B%5Cn%20%20%20%20.container%20%7B%5Cn%20%20%20%20%20%20%20%20--1z%3A%2016px%3B%5Cn%20%20%20%20%20%20%20%20padding-left%3A%208px%3B%5Cn%20%20%20%20%20%20%20%20padding-right%3A%208px%5Cn%20%20%20%20%7D%5Cn%7D%5Cn%5Cn%5Cn%40media%20(min-width%3A%20576px)%20%7B%5Cn%20%20%20%20.container%20%7B%5Cn%20%20%20%20%20%20%20%20--1u%3A%20calc((100vw%20-%20556px%20%2B%20var(--1z))%20%2F%202)%3B%5Cn%20%20%20%20%20%20%20%20--1t%3A%20calc((100vw%20-%20556px%20%2B%20var(--1z))%20%2F%20-2)%3B%5Cn%20%20%20%20%20%20%20%20max-width%3A%20100%25%3B%5Cn%20%20%20%20%20%20%20%20width%3A%20556px%5Cn%20%20%20%20%7D%5Cn%7D%22%2C%22visitorEnabled%22%3Afalse%2C%22visitor%22%3A%22%7B%5Cn%20%20Color(color)%20%7B%5Cn%20%20%20%20if%20(color.type%20%3D%3D%3D%20'rgb')%20%7B%5Cn%20%20%20%20%20%20color.g%20%3D%200%3B%5Cn%20%20%20%20%20%20return%20color%3B%5Cn%20%20%20%20%7D%5Cn%20%20%7D%5Cn%7D%22%2C%22unusedSymbols%22%3A%5B%5D%2C%22version%22%3A%22local%22%7D)

Probably related to this Rust bug: https://github.com/rust-lang/rust/issues/91979. The workaround is to load the native module on the main thread in addition to the worker so that it never gets unloaded.