Closed
Bug 500503
Opened 16 years ago
Closed 16 years ago
when creating a new tab, please show the URL bar instead of a blank white screen
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jmaher, Assigned: mfinkle)
Details
Attachments
(1 file)
585 bytes,
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
upon adding a new tab using the + button, I get a blank white page with a virtual keyboard. This is confusing as the tab strip is gone (agreed this should be the case), the url bar is hidden (oops) and the background is just white. Maybe an awesome bar?
Assignee | ||
Comment 1•16 years ago
|
||
if you start on a page with the toolbar panned down (not floating), the new tab works as expected. The toolbar is ready and waiting.
If the initial tab page has been panned, the new tab page has the same pan, so the toolbar is offscreen.
Almost exactly like bug 500012
This change broke it:
http://hg.mozilla.org/mobile-browser/rev/0908495a295d#l39
Going back to ws.panTo(0, -BrowserUI.toolbarH) should fix it.
Assignee | ||
Comment 2•16 years ago
|
||
This patch switches back to the previous behavior. The hideTabs() was added as a way to minimize the size of the pan, but it's needed.
Assignee: nobody → mark.finkle
Attachment #385211 -
Flags: review?(gavin.sharp)
Updated•16 years ago
|
Attachment #385211 -
Attachment is patch: true
Attachment #385211 -
Attachment mime type: application/octet-stream → text/plain
Updated•16 years ago
|
Attachment #385211 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Comment 3•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
![]() |
||
Comment 4•14 years ago
|
||
Retested with:
Build ID: Mozilla/5.0 (Android; Linux armv7l; rv:10.0a1) Gecko/20111018 Firefox/10.0a1 Fennec/10.0a1
Device: Motorola Droid 2
OS: Android 2.3
Bug is no longer reproducible: awesome screen is displayed with focus in the url bar when trying to add a new tab.
Verifying bug.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•