fix manifest

[patricklx]

fixes #1158

[RobbieTheWagner]

@patricklx was matches all we were missing then? What exactly does this do?

[patricklx]

i'm not sure 😅
thats from https://developer.chrome.com/docs/extensions/migrating/manifest/#update-wa-resources
and the error reported when loading the extension locally into chrome

[RobbieTheWagner]

i'm not sure 😅 thats from https://developer.chrome.com/docs/extensions/migrating/manifest/#update-wa-resources and the error reported when loading the extension locally into chrome

IIRC things worked locally for me, even with manifest v3. You were seeing an error? Does this resolve that error?

[patricklx]

yes, it loads the extension now, but it fails to load on any page...
some csp issue

[patricklx]

I understand now. adding inline scripts directly is not allowed any more. But its possible to load scripts that are specified in the allowed resourced inside the manifest.
I will add fixes for that as well here

[RobbieTheWagner]

Will specifically loading 3-16-0 here break our check where we switch to different versions for older Ember?

[patricklx]

Yes, just testing now. I will change it later

[patricklx]

I think thizis ready.
Let me squash all commits

[patricklx]

Squashed and ready

[patricklx]

this might also fix #1158

[RobbieTheWagner]

@patricklx have you checked to make sure the older versions still boot up for Ember < 3.16?

[RobbieTheWagner]

This looks good to me! Thank you so much for your help 🎉. I just want to make sure we test these changes against some older Ember versions, to make sure loading the old versions works still.

[patricklx]

finally found a website...
http://altrim.github.io/ember-cli-tooltipster/ is using Ember 2.10.1
it loads correctly, uses older ember_debug and ember-inspector.
it loaded first panes-3-16/ember_debug.js, then it detects the version and sends version-mismatch which triggers the loading of older version