Runtime issue: Cannot read properties of undefined (reading 'source')

[JackieHayduk]

<< Please describe how you encountered this issue >>

axe-core version: 4.4.2
axe-extension version: 4.36.2

TypeError: Cannot read properties of undefined (reading 'source')
    at chrome-extension://lhdoppojpmngadmnindnejefpokejbdd/axe-versions/latest/axe.js:12:167249
    at Array.map (<anonymous>)
    at chrome-extension://lhdoppojpmngadmnindnejefpokejbdd/axe-versions/latest/axe.js:12:167219
    at Array.forEach (<anonymous>)
    at chrome-extension://lhdoppojpmngadmnindnejefpokejbdd/axe-versions/latest/axe.js:12:167169
    at Array.forEach (<anonymous>)
    at chrome-extension://lhdoppojpmngadmnindnejefpokejbdd/axe-versions/latest/axe.js:12:167065
    at Array.map (<anonymous>)
    at chrome-extension://lhdoppojpmngadmnindnejefpokejbdd/axe-versions/latest/axe.js:12:166733
    at Array.map (<anonymous>)

[WilcoFiers]

Can you provide some information on how you got this error?

[JackieHayduk]

Hello, I was attempting to "scan part of the page" on a local hosted storybook instance. Thanks, Jackie Please Note: My working hours may be different than yours. Please do not feel obligated to respond outside your normal working hours. (Philadelphia Based | EST) JACKIE HAYDUK

…

______________________________________________ Senior Front End Engineer • Certified Web Accessibility Specialist Philadelphia, PA [image: Hero Digital Logo] <https://herodigital.com/> [image: IAAP Web Accessibility Certification] <https://www.accessibilityassociation.org/s/wascertification>

On Thu, Sep 1, 2022 at 7:01 AM Wilco Fiers ***@***.***> wrote: Can you provide some information on how you got this error? — Reply to this email directly, view it on GitHub <#3627 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOXQ26HU4YI5SBXKX3LLVCDV4CEHXANCNFSM6AAAAAAQBOGMTI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[WilcoFiers]

That'll be difficult to debug. I can't think of anything either related to running on localhost, or running storybook that could cause this issue. @scurker / @schne324 any thoughts?

[scurker]

@JackieHayduk is there any way you could run axe-core manually to see if you get the same issue? That may help us narrow down the problem. In your chrome devtool console, you can try the following where '.selector .to .element is a unique selector to the part of the page you're trying to scan:

await import('https://unpkg.com/axe-core@4.4.2')
await axe.run([document.querySelector('.selector .to .element')], {
  restoreScroll: true,
  resultTypes: ['violations', 'incomplete']
}) 

Do you get any errors when running something similar to the above code example?

[padmavemulapati]

Cannt reproduce with axe-core also it is tracking from the extension, https://github.com/dequelabs/axe-extension/issues/3185 . So closing here