Dan Bjorge

I don't think we'd be able to change axe's default selector resolution behavior outside of a breaking change release, but I do see the utility in it and I think...

Yeah, I think you'd probably have to walk the whole tree at least once - but axe already has to do that anyway for stuff like grid formation, I don't...

> I'd lean more towards a new option, similar to fromShadowDom / fromFrame, rather than a boolean flag. Something like this: I'm fine with using a new option name and...

I think preserving history like that makes sense, but if you want to preserve history across blame boundaries, you're going to need to be very careful about the specific sequence...

> I'm inclined to say we update our .nvm file to use node 24. It only enforces the development version of node so if we need node 24 to publish...

I'm a bit confused; are you suggesting that we do this just as an optimization for cases that involve DOMs with very high branching factors, like your investigation in https://github.com/dequelabs/axe-core/issues/4427...

I agree with Wilco; I think generating "good" (robust/readable) selectors is too important to trade away by default. > Techniques such as Tailwind, which has every individual css prop as...