1254681 - Test that link clickers on Firefox e10s browsers who click links they generated themselves don't encounter issues

Status: RESOLVED WORKSFORME

(Hello (Loop) :: Client, defect, P1)

Comment 1

[Romain Testard [:RT]]

Attachment: Capture d’écran 2016-03-08 à 12.57.46.png

Comment 2

[Romain Testard [:RT]]

Attachment: Capture d’écran 2016-03-08 à 12.57.57.png

Comment 3

[Romain Testard [:RT]]

I get the following from the browser console which makes it look like the e10s panel (prompt user to open a non e10s window) is missing?

OpenGL compositor Initialized Succesfully.
Version: 2.1 INTEL-10.6.31
Vendor: Intel
Renderer: Intel(R) Iris(TM) Graphics 6100
FBO Texture Target: TEXTURE_2D
No stores registered for event type  metricsLogJoinRoom dispatcher.js:88:9
Loop:Error: Tab sharing is not supported for e10s-enabled browsers
Stack trace:
kMessageHandlers.AddBrowserSharingListener@chrome://loop/content/modules/MozLoopAPI.jsm:176:17
LoopAPIInternal.handleMessage@chrome://loop/content/modules/MozLoopAPI.jsm:1174:5
MessageListener.prototype.callListeners@resource://gre/modules/RemotePageManager.jsm:35:9
RemotePages.prototype.portMessageReceived@resource://gre/modules/RemotePageManager.jsm:108:5
MessageListener.prototype.callListeners@resource://gre/modules/RemotePageManager.jsm:35:9
ChromeMessagePort.prototype.message@resource://gre/modules/RemotePageManager.jsm:340:3
 MozLoopAPI.jsm:177
Error getting the windowId: Tab sharing is not supported for e10s-enabled browsers activeRoomStore.js:903:9
ActiveRoomStore<._handleSwitchBrowserShare() activeRoomStore.js:903
(Async: promise callback) ActiveRoomStore<.startBrowserShare() activeRoomStore.js:980
Dispatcher.prototype._dispatchNextAction/<() dispatcher.js:100
Dispatcher.prototype._dispatchNextAction() dispatcher.js:98
Dispatcher.prototype._dispatchNextAction() dispatcher.js:107
Dispatcher.prototype.dispatch() dispatcher.js:72
OTSdkDriver.prototype._onSessionConnectionCompleted() otSdkDriver.js:380
eventing/self.once/handleThisOnce() sdk.js:766
executeListenersAsyncronously/</<() sdk.js:999
[12]</callbacks.callAsync/<() sdk.js:1371
(Async: setTimeout handler) [12]</callbacks.callAsync() sdk.js:1370
executeListenersAsyncronously/<() sdk.js:995
executeListenersAsyncronously() sdk.js:988
browserEventing/api.dispatchEvent() sdk.js:1105
eventing/self.dispatchEvent() sdk.js:803
[209]</SessionHandle.Session/connectMessenger/<() sdk.js:35628
onConnectComplete() sdk.js:26932
RaptorSocket/this.connect/</</<() sdk.js:27143
[163]</Dispatcher.prototype.triggerCallback() sdk.js:26271
SessionDispatcher/<() sdk.js:27496
executeListenersSyncronously/<() sdk.js:1040
executeListenersSyncronously() sdk.js:1039
browserEventing/api.trigger() sdk.js:1116
eventing/self.trigger() sdk.js:832
[163]</Dispatcher.prototype.dispatchSession() sdk.js:26355
[163]</Dispatcher.prototype.dispatch() sdk.js:26314
webSocketReceivedMessage() sdk.js:28780
NativeSocket/webSocket.onmessage() sdk.js:28009
(Async: EventHandlerNonNull) NativeSocket() sdk.js:27994
[179]</RumorSocket/connect() sdk.js:28819
[179]</RumorSocket/rumorSocket.connect() sdk.js:28862
RaptorSocket/this.connect() sdk.js:27063
[209]</SessionHandle.Session/connectMessenger() sdk.js:35586
[209]</SessionHandle.Session/onSessionInfoResponse<() sdk.js:35686
tryCatcher() sdk.js:11194

OpenGL compositor Initialized Succesfully.
Version: 2.1 INTEL-10.6.31
Vendor: Intel
Renderer: Intel(R) Iris(TM) Graphics 6100
FBO Texture Target: TEXTURE_2D

Comment 4

[Dan Mosedale (:dmosedale, :dmose)]

I suspect that RT's guess is correct.  Presumably this is not reliably reproducible, given the steps RT listed are what users do every single time they use product, so I suspect our best bet is speculate that this will go away after the e10s work is done, which is arguably embodied by bug 1252621.

Comment 5

[Romain Testard [:RT]]

Retest and close

Comment 6

[Romain Testard [:RT]]

I am closing since I cannot reproduce this anymore.