-
Notifications
You must be signed in to change notification settings - Fork 363
False Negatives running in chrome browser, but not running through phantomjs #126
Comments
@alice the Chrome Extension seems to be directly impacted by this bug. |
The problem appears to be in I think this assumption is wrong: // Descend into node:
// If it has a ShadowRoot, ignore all child elements - these will be picked
// up by the <content> or <shadow> elements. Descend straight into the
// ShadowRoot. An element could have both regular DOM child elements AND shadow DOM. It could be as simple as commenting out the return statement on line 148 of |
@ckundo I fixed this in my existing pull request - sorry I wasn't sure how to create an entirely isolated pull request from my fork. I added some unit tests but they only function when run on a platform that supports shadow dom - in other words they do nothing in the current version of phantomjs. |
@ricksbrown Could you pull this fix into a separate branch and create a new pull request for it? (Create a new git branch locally, push that up to your repo, and you should see an option in the UI to create a new PR.) |
@ricksbrown Also, I checked, and it's not quite accurate that "An element could have both regular DOM child elements AND shadow DOM" - what's happening with AdBlock Plus is that it's inserting a shadow root containing only a So what actually needs to be fixed is that in this if-block https://github.com/GoogleChrome/accessibility-developer-tools/blob/master/src/js/AuditRule.js#L169 we need to check first for (I couldn't understand the spec, so I asked one of the spec authors to explain it to me... perks of working where I do!) |
@alice I created a pull request but hadn't read your additional comments. I'll rework the pull request, ignore it for the moment, I'll post back here when I'm done. |
This reverts commit 3a3da9a.
@ricksbrown I've also been fiddling with this (based off your original PR) - depending how things go I might send you a PR to incorporate into your PR :) |
When we do
axs.Audit.run()
to Google.com as in #125 we get a fewFAIL
s, but if we run the same script in google.com in Chrome's console we do not:This may be relevant and high priority for the Chrome Extension.
The text was updated successfully, but these errors were encountered: