Eric Tsai (no more review request accepted) Reporter
	Description • 9 years ago

Current control mode is for dispatch different event to app, for example, touch move for browser but gesture to page up/down for control home screen.

	Luke Chang [:lchang] (inactive) Assignee
	Comment 1 • 9 years ago

We've decided smart-system will notify Gecko of the mode-changed status via "mozContentEvent" event as follows:

{
  type: 'control-mode-changed',
  detail: {
    cursor: true / false
  }
}

And Gecko can request system to report the status actively by using "mozChromeRemoteControlEvent" as follows:

{
  type: 'request-control-mode',
  detail: null
}

	Luke Chang [:lchang] (inactive) Assignee
	Comment 2 • 9 years ago

This bug will be addressed in Gaia side so take it over from Eric.

	Luke Chang [:lchang] (inactive) Assignee
	Comment 4 • 9 years ago

Comment on attachment 8672542 [details]
[gaia] luke-chang:1207995_tv_provide_control_mode > mozilla-b2g:master

Hi Rex,

Could you please take a look at this? Thanks.

This patch hard-codes to detect if the currently-focused element is the browser app. If yes, it reports "cursor: true" to Gecko, and vice versa. So that Gecko can determine whether or not it needs to draw a cursor on it.

	Luke Chang [:lchang] (inactive) Assignee
	Comment 5 • 9 years ago

(In reply to Luke Chang [:lchang] from comment #1)
> And Gecko can request system to report the status actively by using
> "mozChromeRemoteControlEvent" as follows:
> 
> {
>   type: 'request-control-mode',
>   detail: null
> }

Protocol changed:

{
  action: 'request-control-mode'
}

	KM Lee [:rexboy] (inactivate after Sep. 22)
	Comment 6 • 9 years ago

Comment on attachment 8672542 [details]
[gaia] luke-chang:1207995_tv_provide_control_mode > mozilla-b2g:master

Looks good to me. Thank you!

	Luke Chang [:lchang] (inactive) Assignee
	Comment 7 • 9 years ago

(In reply to Luke Chang [:lchang] from comment #5)
> (In reply to Luke Chang [:lchang] from comment #1)
> > And Gecko can request system to report the status actively by using
> > "mozChromeRemoteControlEvent" as follows:
> 
> {
>   action: 'request-control-mode'
> }

Let me explain this more.

In case the HTTP server is, for some reason, initialized or rebooted after system app is loaded, it can retrieve the current control mode immediately by utilizing this event instead of waiting for the next "control-mode-changed" event.

	Luke Chang [:lchang] (inactive) Assignee
	Comment 8 • 9 years ago

tests passed: https://treeherder.mozilla.org/#/jobs?repo=gaia&revision=60feee58bd90c7ac0c9e4a554271e190599979c5

landed on master: https://github.com/mozilla-b2g/gaia/commit/ddc269c6c3ac40ee7216f7bfd2d30d22bc49071f