Closed
Bug 777893
Opened 13 years ago
Closed 13 years ago
b2g desktop builds have no network access
Categories
(Firefox OS Graveyard :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dietrich, Unassigned)
Details
(Whiteboard: b2g-desktop-builds)
No description provided.
|
Reporter | |
Updated•13 years ago
|
Priority: -- → P1
|
|
Reporter | |
Updated•13 years ago
|
Whiteboard: b2g-desktop-builds
How are you testing network access? What specifically is the result?
|
|
Reporter | |
Comment 2•13 years ago
|
||
Was testing via browser. No user feedback, nothing in error console, just get a white content area.
Clicking reload icon does give: Timestamp: 8/8/12 11:03:18 PM
Error: TypeError: this.currentTab.dom.reload is not a function
Source File: http://browser.gaiamobile.org:7999/js/browser.js
Line: 459
Possibly unrelated though.
|
|
Reporter | |
Comment 3•13 years ago
|
||
Ah I do see this on browser startup:
Timestamp: 8/8/12 11:07:49 PM
Error: NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIDOMNavigatorSystemMessages.mozSetMessageHandler]
Source File: http://browser.gaiamobile.org:7999/js/browser.js
Line: 1320
That looks plausible.
Blank content area can mean content-process crash. Launching b2g from the command line sometimes gives better information.
|
|
Reporter | |
Comment 5•13 years ago
|
||
This wfm on latest desktop nightly build -> resolved WFM.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•