Closed Bug 855021 Opened 11 years ago Closed 11 years ago

[Browser] tab tray doesn't open upon first launch

Categories

(Firefox OS Graveyard :: Gaia::Browser, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.0 unaffected, b2g18-v1.0.1 fixed)

VERIFIED FIXED
blocking-b2g tef+
Tracking Status
b2g18 --- fixed
b2g18-v1.0.0 --- unaffected
b2g18-v1.0.1 --- fixed

People

(Reporter: nhirata, Assigned: benfrancis)

References

Details

(Keywords: dogfood, Whiteboard: [fromAutomation] QARegressExclude)

Attachments

(2 files)

Attached file logcat
## Environment :
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/28b048ffb7a7
Gaia   ace1eb32a313da1232bbdf9cff2581a4b036356d
BuildID 20130326070204
Version 18.0
Unagi
  
## Repro :
1. make sure browser is not open at all using the task manager
2. launch browser
3. immediately after launch try opening the tab tray

## Expected :
tab tray opens

## Actual :
tab tray doesn't open; the arrow indicator points as if it was open

## Note :
1. http://www.youtube.com/watch?v=AnQTDM2rAD0&feature=youtube_gdata_player
2. master is not affected.
work around is to change orientation and then retry as shown in video.
blocking-b2g: --- → leo?
affects 1.0.1

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/4931ec89ebbe
Gaia   c33b1f8b60edc223ba86dd22f912effee990132a
BuildID 20130327070203
Version 18.0
blocking-b2g: leo? → tef?
blocking-b2g: tef? → tef+
Whiteboard: [fromAutomation]
This appears to be a regression; QA - we could really use the regression window.
My own testing confirms bug 853444 (which has more info in general):  if I wait for a page to load entirely (no more scrolling progress bar), *then* I can open more tabs.  Once *one* tab is fully loaded, I can open other tabs.

Regression window is at https://bugzilla.mozilla.org/show_bug.cgi?id=853444#c5 as Alex noted.

David, should Ben take this when he gets back on Wednesday?
Assignee: nobody → dscravaglieri
I've also see this not on first launch -- in particular, after opening a link from twitter (which opens the link in a new tab), I couldn't get the UI to close that tab and get back to twitter.


(In reply to Andrew Overholt [:overholt] from comment #6)
> David, should Ben take this when he gets back on Wednesday

Whatever caused this should get backed out well before Wednesday; the constant stream of bugs like this (breaking basic functionality) is what makes it hard for people to use builds as dogfood, which makes it less likely that we'll *find* the next level of bugs.
Keywords: dogfood
Assignee: dscravaglieri → bfrancis
Wow, it took me a while to figure out how this happened, but it seems that bug 849280 was uplifted but is subtly dependent* on bug 830644 which wasn't.

Bug 849280 itself was uplifted in order to fix a regression which was introduced by uplifting bug 836647 so I wouldn't recommend backing it out.

The obvious way to fix this is to uplift bug 830644, but I'm not sure where this chain of dependencies is going to end! I think these branches have existed too long, they're diverging too far away from master. Hopefully the madness will end soon.

*By way of explanation, bug 849280 removed a call to the handleWindowResize method which sets the transform on the #main-screen div to move it off the screen because it was dead code after the changes made in bug 830644.
Blocks: 830644
No longer blocks: 830644
Depends on: 830644
No longer depends on: 830644
On second thoughts, that's not going to work. The commit that we need (e0d4130a06481c881cbac587bf856f3730b4e505) has a lot of other dependencies.

I think we're going to have to create a bugfix specific to the v1-train and v1.0.1 branches which will never apply to master.
This is a bugfix for the v1-train and v1.0.1 branches but isn't needed on master.

The pull request is agains the v1.0.1 branch so the commit will need cherry picking for v1-train as well.
Attachment #732979 - Flags: review?(dale)
Does this also fix the bookmarks UI not showing up when I click in the URL bar, or should I file a separate bug for that?
> Does this also fix the bookmarks UI not showing up when I click in the URL bar, 
> or should I file a separate bug for that?

I havent been able reproduce any bug that looks like that before or after this patch so yeh file separately
Thanks Dale, https://github.com/mozilla-b2g/gaia/commit/73c24b0b8fa34da37e5cbdda188595c2bd9b4c25

This will need uplifting to v1-train (original commit is df74281954ea1b3b03526bc70deba84e42c1b482)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
v1-train: bf6b8e306b1eea4b6b8ae206eca4716ce70e1262
Whiteboard: [fromAutomation] → [fromAutomation] QARegressExclude
Verified fixed in ikura device with build identifier 20130414230203 from V1.0.1 and gaia commit 3a7dda889.
Status: RESOLVED → VERIFIED
Attachment mime type: text/plain → text/x-github-pull-request
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: