761934 - Popcap games don't work out-of-process in gaia

Status: RESOLVED DUPLICATE of bug 774139

(Firefox OS Graveyard :: General, defect)

Description

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

STR
 (1) Load "Tower Jelly" gaia app out of process.
 (2) Try to start a game.

It's possible to navigate to the "START GAME" option, but not to actually click it.  I suspect mousedown/mouseup are going through, but (click?) isn't.  Or something.

Might be a gecko event-processing bug, but dropping into B2G component first.

Comment 1

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Attachment: Gaia test

Hmmmm .... this test seems to show that onclick is being fired.

(I know this code is running out of process because console.log doesn't work :/.)

Comment 2

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Because of bug 763340, it's possible that there's an exception being thrown that we're missing because of lack of console service.

Comment 3

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Bug 762240

Comment 4

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

smaug, this bug has to be caused by some difference in the DOM events we dispatch to content in the in-process vs. out-of-process cases.  Can you suggest a good way to debug this problem?

If there's a central location that we dispatch DOM events to content from, then I'd like to log the events that are dispatched from there.  Maybe we already have that kind of logging code?

Comment 5

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

<bz> cjones: nsEventDispatcher
* dzbarsky ([e-mail]) has joined #content
* josh ([e-mail]) has joined #content
<bz> cjones: Log in Dispatch and DispatchDOMEvent, and you should get everything

Comment 6

[Olli Pettay [:smaug][[e-mail]]]

nsEventDispatcher::Dispatch gives you all the dispatched events.

Comment 7

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

This is a difference in behavior between same-process/cross-process event delivery that's breaking some extremely simple apps.  This should block.

Comment 8

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

(In reply to Chris Jones [:cjones] [:warhammer] from comment #7)
> This is a difference in behavior between same-process/cross-process event
> delivery that's breaking some extremely simple apps.  This should block.

This doesn't seem to be games specific at all -- just event delivery seems to be broken.  If this doesn't work, how does anything?

Comment 9

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Felipe and I discovered that we don't dispatch raw touch events to content processes, even though |window.TouchEvent| will be nonnull.

So that's probably what's broken here!  Argh.

Comment 10

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

These guys work with the patch in bug 774139.