Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Unpacked _locales #776

Open
erosman opened this issue Mar 5, 2025 · 3 comments
Open

Proposal: Unpacked _locales #776

erosman opened this issue Mar 5, 2025 · 3 comments
Labels
needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time neutral: safari Not opposed or supportive from Safari

Comments

@erosman
Copy link

erosman commented Mar 5, 2025

Proposal: Unpacked _locales

Simply an idea for further discussion

Background

Almost all free extensions maintain their _locales through user contributions. In most cases, it is not practical to maintain and pack 100s of locales with the extension.
The idea is to provide an alternative method of providing locales where users can upload their preferred individual locale, to be used by the extension.

Benefits

  • Smaller extensions (for developers, browsers, & web stores)
  • Easier maintenance
  • Users can create & use their own locales

Requirements

Subject to a consensus between bowsers to provide the feature ...

  • Additional extension storage for the user locales e.g. _userLocales
  • Browsers to internally combine _locales & _userLocales
  • A method to upload messages.json to the above storage
    • It can be an API user-interface via the extension
    • It can be a browser user-interface under the extension management
@github-actions github-actions bot added needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time needs-triage: safari Safari needs to assess this issue for the first time labels Mar 5, 2025
@xeenon xeenon added neutral: safari Not opposed or supportive from Safari and removed needs-triage: safari Safari needs to assess this issue for the first time labels Mar 5, 2025
@xeenon
Copy link
Collaborator

xeenon commented Mar 5, 2025

This is mostly out of scope for this group — as this relates to packaging and distribution — this can also be done with browser implementations today. The API aspect is the only area that could be considered here, but I'm not sure there is any demand for this support from users.

I would be neutral to opposed for Safari.

@erosman
Copy link
Author

erosman commented Mar 6, 2025

This is mostly out of scope for this group — as this relates to packaging and distribution — this can also be done with browser implementations today.

@xeenon Can a user install a messages.json locale for an installed extension with the current API?

To clarify ...

  • An extension is packed with _locale/en/messages.json only
  • de/messages.json is available to download from a repository
  • Can a user add the above to his/her installed extension?

@xeenon
Copy link
Collaborator

xeenon commented Mar 6, 2025

This is mostly out of scope for this group — as this relates to packaging and distribution — this can also be done with browser implementations today.

@xeenon Can a user install a messages.json locale for an installed extension with the current API?

To clarify ...

  • An extension is packed with _locale/en/messages.json only
  • de/messages.json is available to download from a repository
  • Can a user add the above to his/her installed extension?

That is not possible today, but also something any browser could add UI to allow. I don't see a benefit for an API to allow the extension to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage: chrome Chrome needs to assess this issue for the first time needs-triage: firefox Firefox needs to assess this issue for the first time neutral: safari Not opposed or supportive from Safari
Projects
None yet
Development

No branches or pull requests

2 participants