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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃寪 Allow language override from viewer context #28182

Merged
merged 2 commits into from May 12, 2020

Conversation

Enriqe
Copy link
Contributor

@Enriqe Enriqe commented May 4, 2020

Closes #27023

Original description:

In platform contexts, it makes sense for document-rendered system-level user interfaces to be consistent across documents. This PR allows an AMP viewer or story player to specify a fragment parameter to indicate the language to be used, falling back to the document's language if unspecified.

Follows up on #27990 #27053

@Enriqe
Copy link
Contributor Author

Enriqe commented May 5, 2020

I've hit a bit of a hiccup here. There's a circular dependency between services.js and localization.js. This is because in my last change I import LocalizationService in services.js to register it, and in this change I want to use Services.viewerForDoc inside localization.js.

So my plan is to delete the dependency in services.js by installing the LocalizationService in the extensions individually. This will come as a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow viewers to override system language
6 participants