Tony Ross

For anyone else trying to work around this for a monorepo scenario, I was able to do so by adding my `extends` clause in a local `package.json` and putting the...

@webhintio/contributors I've been giving this some thought and had a slightly different idea. What about letting the *site* choose the configuration instead? E.g. the online scanner could check for a...

@LB22 Thanks for the feedback! @hxlnt think we could get some design resources to help us pick some dark mode colors for the site? I'm also a dark mode fan...

@daviddossett is this something your team might be picking up soon? Or would you be interested in external contributions? I ask because we recently needed this control for some work...

Thank @njnithin for following up on this! @mliao95 @codepo8 this is different than our prior source mapping issues and is more of a feature request. Specifically, this is about adding...

@mavigozler FYI if you also want to just turn off feedback for Internet Explorer, you can update your target browsers either in your package.json or .hintrc file. E.g. this package.json...

@codepo8 I dug into this a bit more on the webhint side and the issue for the persistent error when pairing `grid-template-columns` with `-ms-grid-columns` is that webhint is able to...

Yes, the `.hintrc` can be configured to ignore reports for specific CSS properties (and we have a set of defaults we can add to). But that would fully eliminate the...

I assume they picked up the suggested `.hintrc` to exclude IE earlier in the thread. We'll be making this better for all users shortly by excluding IE by default in...

@CubeBR if it's related to CSS ***without*** source maps there is a known issue with formatting that's affecting all Chromium-based DevTools (see [this Chromium bug](https://bugs.chromium.org/p/chromium/issues/detail?id=1309588) which was recently fixed). The...