Tony Ross

@mnosal, this part of the log looks related and indicates we had trouble processing a particular file you had open: > AnalyzerError: Unable to parse axe results null The `axe`...

Yeah, I think pointing this at the `` element (if present) would make more sense, the `` element otherwise, and finally falling back to the start of the document if...

Thanks for the report @jSadoski! I think this is hitting the same underlying problem as this webhint bug and will need to be fixed by us: https://github.com/webhintio/hint/issues/5082#issuecomment-1136344296. In that case...

@vidorteg thinking about this some more, I suspect fixing the assumption in `hint-meta-charset-utf8` will resolve the error, but still result in a false-positive because the meta tags get pushed to...

@darkgrayknight thanks for the feedback! While we don't have a UI for it yet, the webhint integration can be configured using webhint's existing config file format by adding a `.hintrc`...

@sarvaje no strong preference on my part. I think a GitHub Action sounds great if you think that'll work best. I'd also be happy with an Azure Pipeline since we're...

Hey @ruppysuppy sorry for the slow response. Taking a look at this I don't see the AST information available either. I think we may need to do some more work...

Thanks for the report @AndreasJacobsen! I'm not immediately sure what's going on here, though I do wonder if the monorepo structure is somehow confusing the extension. The only thing that...

@captainbrosset, per #2621 we should be allowing either, so something's definitely gone awry 🤔 I'm wondering if we picked up a dependency update that altered this (though it should have...

Thanks for the report @ivanagui2! I'm not sure what's going on yet other than it appears webhint is having trouble finding the `@hint/configuration-development` package. Also no luck reproducing the issue...