Closed
Bug 860284
Opened 12 years ago
Closed 12 years ago
Gaia browser broken against mozilla-central
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: bjacob, Unassigned)
References
Details
Well, I'm using the graphics branch, but it should be no different from mozilla-central in this respect, and people on #b2g confirmed similar symptoms on mozilla-central.
Some of the symptoms are:
- no 'Browser' process in 'adb shell b2g-ps'
- pinch-zoom not working
- browser does not remember any history (it seems)
I need a working Gaia browser in a separate process to reproduce/test graphics bugs.
Comment 1•12 years ago
|
||
Could you try changing this line: https://github.com/mozilla-b2g/gaia/blob/c998c9ce045a8a858b7e155944b7b4f6573d2c22/apps/browser/js/browser.js#L1437 to iframe.setAttribute('mozbrowser', true)? if this fixes the problem, it could because iframe WebIDL landed on central, and Browser App needs corresponding change. (The change landed in Gaia's master branch.)
Comment 2•12 years ago
|
||
That seems to fix the problem.
Comment 3•12 years ago
|
||
What branch of gaia are you using, and will the WebIDL changes be uplifted to 1.0.1 and 1.1?
If so, then this may become tef+ or leo+ in future and require an uplift.
Reporter | ||
Comment 4•12 years ago
|
||
For the record, I was using the default Gaia from B2G 1.0. I didn't realize that I should switch to "gaia master" or however it's called.
Comment 5•12 years ago
|
||
Patrick,
What were the bug numbers for the Gecko and Gaia changes in mozilla-central and gaia? We should mark the dependency in case one of them gets uplifted.
Flags: needinfo?(pwang)
Comment 6•12 years ago
|
||
Bug 844169 is Gecko change and Gaia change is in Bug 853845. None of them are marked to uplift.
Flags: needinfo?(pwang)
Comment 7•12 years ago
|
||
Shouldn't be an issue if you use the version of Gaia with the corresponding version of Gecko.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•