Greg Bruening

Results 16 comments of Greg Bruening

@Bkucera That makes sense (and good to know the issue I was hitting wasn't just me). I just find it surprising that ally wouldn't have a solution for this since...

@Bkucera Secondary note - while perusing ally.js issues and backlog things it looks like they have open collaboration with jQuery UI to actually replace JQUI's own focusable/tabbable with ally's versions...

@Bkucera Is the issue around `includeOnlyTabbable: true,` this option from a11y.js? I saw their default is false and their demo seems to work as I would expect (tabbing passes -1...

@Bkucera Makes sense - here's a quick test project that tests tabbing before, after, and over a -1 element with the plugin - https://github.com/geebru/cypress-tab-test Or here's the Cypress spec file...

@Bkucera Since Cypress has removed (at least temporarily) the native events item from the active roadmap, is there a chance this issue could be addressed since it sounds like it...

@Bkucera As a note I've started just playing with ally.js instead of trying to replace it with tabbable.js. It does include `focusable` in addition to `tabSequence` which does correctly see...

For extra context here is the point where I noticed this occuring: In GitHub, and locally, this was the history I expected to see (minus release commits of course): ![image](https://user-images.githubusercontent.com/806033/159924437-ce9710e9-8410-4909-ad46-8621653ead7d.png)...

For outright errors yeah, but I mean in the realm of setting SCSS "rules" such as only use SCSS comments, lower case class names, etc. that are more personalized. That...

I've had my eye on this - https://github.com/causes/scss-lint Still doing some tests with it when I have time in between projects but seems to be the best out there.

@kristerkari To be honest I figured _this_ would be the separate plugin to do so since it handles SCSS directly. But I do see your point that deprecating things in...