ReferenceError: axs is not defined about accessibility-developer-tools-extension

[alice]

@bezoerb Would you be able to give some more details about your local dev environment? I'd like to try and reproduce this.

[bezoerb]

Hi @alice,
i think it's more about the reachability from the internet than my local dev environment.
I tried this on OSX Mavericks with my Webserver running on localhost as well as on Windows with a preview Webserver which was secured through htaccess basic authentication.

It seems like that error pops up every time i'm on a page which isn't reachable from outside.

[alice]

@bezoerb This is with the current version of the extension from Chrome Web Store (2.9.2), right? I'm trying to reproduce by running a python SimpleHTTPServer on localhost:8000, browsing there and running the audit, but I don't see this issue (and in fact I often use this set-up to test the extension, so I'm surprised it's not working for you). Are your local/dev instances unusual in any other way?

[bezoerb]

@alice Yes, this is the current version.
Unfortunately i can't reproduce the error locally at the moment although i did not change my environment.
I'm running Apache2 as Webserver but i think this doesn't make a difference.
As soon as i can narrow down the source of the issue i'll let you know.

Thanks

[alice]

@bezoerb Sure, please do let me know once you have some reliable reproduction steps.

I have noticed that sometimes the extension is a little flaky for a few minutes after installation or upgrade, and I haven't worked out what's causing that yet - usually it goes away after a little while, so of course it's frustratingly difficult to debug, but the symptoms look similar to this (essentially a failure to inject the content scripts which provide the back end to the audit and the sidebar pane).

[espeedg]

On http://play.google.com/store, on the first request the error doesn't show up, but every subsequent refresh the error appears three times in 3 different places. This happens every time for me.

[alice]

@espeedg Thanks for the repro steps! I think that might be a separate issue, but definitely one worth fixing, so I'll definitely take a look.

[alice]

Pulled the reload issue out into #16 in case it does turn out to be separate.