chrome.languageSettingsPrivate API Proposal

1 view
Skip to first unread message

Michael Giuffrida

unread,
May 8, 2015, 9:21:01 PM5/8/15
to apps-dev, Security Enamel, Shu Chen, Alexander Alekseev, chromium...@chromium.org
Hi apps-dev'ers,

I'm proposing a languageSettingsPrivate API for use by the new material design Settings UI and any other UI/apps that may be interested (e.g. OOBE, Get Help app).

I've worked feedback from shuchen@ and kalman@ into the proposal and the draft IDL.

This is a private API intended for getting and changing language and input method settings.

Thanks!
Michael

Benjamin Kalman

unread,
May 11, 2015, 8:10:10 PM5/11/15
to Michael Giuffrida, apps-dev, Security Enamel, Shu Chen, Alexander Alekseev, chromium...@chromium.org
lgtm

Alexander Alekseev

unread,
May 12, 2015, 1:10:52 PM5/12/15
to Michael Giuffrida, apps-dev, Security Enamel, Shu Chen, Alexander Alekseev, chromium...@chromium.org
re-sending from @chromium.org .

On Tue, May 12, 2015 at 8:09 PM, Alexander Alekseev <ale...@google.com> wrote:
docs.google.com thinks I'm Anonym for whatever reason, so I'd comment here:

Do you know anyone else, internal or external, that is also interested in this API?

OOBE could use this to avoid some chrome.send calls.

This is questionable, as you're proposing Extension API and OOBE is not an extension.
Also, OOBE sometimes (most of the times) is able to switch language immediately on request.
This requires re-initialization of all extensions, so it is probably not suitable for Extension API.

Mustafa Emre Acer

unread,
May 12, 2015, 3:43:26 PM5/12/15
to Alexander Alekseev, Michael Giuffrida, apps-dev, Security Enamel, Shu Chen, chromium...@chromium.org
Security lgtm.

To unsubscribe from this group and stop receiving emails from it, send an email to apps-dev+u...@chromium.org.

Michael Giuffrida

unread,
May 12, 2015, 3:49:15 PM5/12/15
to Alexander Alekseev, Michael Giuffrida, apps-dev, Security Enamel, Shu Chen, chromium...@chromium.org
thanks, I've removed that answer. But note that Web UI can be given permissions to call extension APIs, which is how we'll use this in Settings initially..

On Tue, May 12, 2015 at 10:09 AM, Alexander Alekseev <ale...@google.com> wrote:
docs.google.com thinks I'm Anonym for whatever reason, so I'd comment here:

Do you know anyone else, internal or external, that is also interested in this API?

OOBE could use this to avoid some chrome.send calls.

This is questionable, as you're proposing Extension API and OOBE is not an extension.
Also, OOBE sometimes (most of the times) is able to switch language immediately on request.
This requires re-initialization of all extensions, so it is probably not suitable for Extension API.
On Sat, May 9, 2015 at 4:20 AM, Michael Giuffrida <mich...@chromium.org> wrote:
Reply all
Reply to author
Forward
0 new messages