I sent a CL for this issue.
https://codereview.chromium.org/2738373002

Has the API change gone through the review process?

http://www.chromium.org/developers/design-documents/extensions/proposed-changes/apis-under-development

Also, note: unless this is a concern for Chrome OS apps, it might not make a lot of sense to add this since desktop apps are scheduled for deprecation.

I think it's also necessary for Chrome OS apps.
Could you help me to make a world-editable copy of the document [1] so that i can start drafting the API proposal.

[1] https://docs.google.com/a/chromium.org/document/d/1VJrcI0ZFqN2x6eSamdoflODgn0EvqYfr8_jHCSCn9Xg/edit

If you don't have a chromium.org account and your @intel account does not allow sharing of the document globally, I would suggest using a gmail account for the document.

Also see  Issue 470669  .

Yes, i have paid attention to this issue-470669, and i think my cl will be useful for fixing it, i will try to it after landing the cl.

I still don't receive any comments from App & Extensions approver about the new API proposal, should i continue ping?

Apologies, but this is pretty low on my priority list and this week is not
a good week for me. I can make a comment on the apps list next week and try
to solicit a response from someone on that team. (They are also spread very
thin).

@stevenjb -- A gentle reminder. Is there any update on this issue.

Thanks!

Could you update this issue with the following:
1. Please confirm that the behavior exists on Chrome OS
2. If it does, please check 'Chrome' under OS and change the status from Unconfirmed to Untriaged

Then the Apps team should be able to triage it when they have a chance.