Specify the hierarchy of files

[ariasuni]

As far as I know, a WebExtensions is a hierarchy a files with:

• As its root, a manifest.json
• As its root also, an optional _locales directory
• All other files referenced by the manifest or the APIs (e.g. in tabs.executeScript) must be in the root or in a subdirectory.

A note could be added that since several browsers distribute extensions as zip, the limitation of this compression format should be taken into account (no need to add more details).

Sounds simple enough to describe, if I didn’t forget anything.

[xeenon]

We should avoid many specifics about the distribution format, since that is out of scope in the charter, but alluding to any limitations might be fine.

[carlosjeurissen]

A resource on the features and limitations per browser would still be very helpful for every developer. Yet this spec might not be the best place for that indeed. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

…

On Thursday, September 2nd, 2021 at 15:32, Timothy Hatcher ***@***.***> wrote: We should avoid many specifics about the distribution format, since that is out of scope in the charter, but alluding to any limitations might be fine. — You are receiving this because you are subscribed to this thread. Reply to this email directly, [view it on GitHub](#64 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAH5PO7XUCXC3F2X57FZRXTT754GBANCNFSM5CP6OPNA). Triage notifications on the go with GitHub Mobile for [iOS](https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675) or [Android](https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub).

[dotproto]

TODO: assign @oliverdunk to this issue once we figure out why we can't ;)

[dotproto]

Another important (and possibly non-normative) note is that casing can lead to filename collisions in certain operating systems. This is occasionally a source of confusing bugs for extension developers. One practical (albeit boring) way to avoid these issues is to ensure that all paths and filenames are lowercase.

[dotproto]

I was about to note that Chrome requires that background service workers are located in the extension's root, but it looks like we resolved that issue: https://crbug.com/1136582

[Jack-Works]

And any files starts with _ excludes _locales will be rejected by Chrome