1192797 - [e10s] getCurrentPosition returning <unavailable>

Status: NEW

(Core :: DOM: Content Processes, defect)

Description

[Ada [:adalucinet]]

Reproducible with latest Developer Edition 41 and Nightly 42, both from 2015-08-09
Affected platforms: Windows 7 64-bit, Ubuntu 14.04 32-bit and Mac OS X 10.10.4

Steps to reproduce:
1. Launch Firefox with e10s enabled.
2. Enable the Browser Console (Cmd/Ctrl + Shift + J).
3. Navigate to http://davidwalsh.name/demo/geolocation.php
4. Click on 'Get My Location' button and Share your location when prompted.

Expected result: Current position is displayed in Browser Console.
Actual result: 'Your position:  <unavailable>' thrown by geolocation.php:26 in Browser Console.

Additional notes:
1. Works with e10s disabled.
2. Not a regression - reproduces back to Nightly 2014-11-07 when electrolysis was first enabled by default.

Comment 1

[:garvan]

The simplest testing method I know of is to load http://www.example.com, open the dev tools (option-cmd-i on the mac) and do a manual js request of the current position.
The output looks like this on e10s with mac 10.10.4 for me:

> navigator.geolocation.getCurrentPosition(function(position) {
					console.log('Your position: ', position);
				});
> undefined
> Your position:  Position { coords: Coordinates, timestamp: 1439214551006 }

Comment 2

[Josh Matthews [:jdm]]

What's curious to me that the web console shows an actual position, while the browser console gets a `<unavailable>` error. I'm not even sure how that error is reaching the browser console; I would expect it to go to the web console.

Comment 3

[Josh Matthews [:jdm]]

Oh, this is a limitation of serializing data over e10s: http://mxr.mozilla.org/mozilla-central/source/toolkit/components/processsingleton/ContentProcessSingleton.js#47 . Fascinating!