The purpose of this API is to allow extensions (e.g. ChromeVox) to handle a number of ChromeOS system events like login, wake-up from sleep and system update.
There are two issues on crosbug.com that may require this API to be implemented.
There are two ways to solve these issues.
I prefer 2. because handling events in extension’s JS code is more flexible and this kind of API may be useful for purposes other than accessibility.
This is a client side feature, and doesn’t make much sense to add to HTML5
I’m not sure if this API is covering the all necessary system events.
No new UI is needed for this API.
AFAIK, there is no security risk about this API.
Hard-coding event handler in C++ on Chromium tree as described above.
All APIs below will be implemented on ChromeOS platform only.
The namespace ‘experimental.system’ is intended to be used to contain system level methods and events. The term ‘system level’ is to mean that those methods and events are not suitable to be handled by windows, tabs, omnibox or any other specific controls on the screen. As the word ‘system’ suggests, this namespace is intended to contain Chromium’s core, low-level, OS-like features only.
// handling the result;