928433 - [Meta] Move more mozChromeEvent into mozBrowser events

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[(inactive after 6/18) Alive Kuo [:alive]]

There's a discussion about removing mozChromeEvent long time ago.
I feel that we should move some app/frame specific event into mozBrowser events to have a better world other than guessing the target by manifestURL or origin, which is bad.

The list of proposed events in my mind now is:
1. Notification
   - Yes, why not? If we want to do "click the notification to go to the app", why does app needs to do relaunch themselves? If we know who fires the notification we could do this in system app.
2. Payment/Identity - app/page specific without doubt.
3. ActivityStart - Though only foreground app could trigger an activity, but maybe someday we would have multiple foreground apps. This one is negotiable.
4. Permission - Already a bug about this.
5. Recording-Status - In gUM we want to know who is doing getUserMedia, we need to know recording-start/recording-end events.

Comment 1

[BMO Automation]

Firefox OS is not being worked on