Closed
Bug 591927
Opened 14 years ago
Closed 14 years ago
"Search With" dialog keeps removing menu items on switch of AwesomeScreen panes and or rotation
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: aaronmt, Assigned: vingtetun)
Details
Attachments
(1 file)
2.96 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Mozilla/5.0 (Android; Linux armv7l; rv:2.0b5pre) Gecko/20100830 Namoroka/4.0b5pre Currently in the build above, I noticed a new "Search With" dialog that appears when I tap the Menu button on my Android device within the AwesomeScreen. On first tap of my devices menu button, I see the following menu items: "Google, Amazon.com, Twitter, Wikipedia" If I dismiss this menu item, switch panels from All Pages to Bookmarks, and open the menu again, Wikipedia is removed. If I dismiss this menu item, switch panels from Bookmarks to History, and open the menu again, Twitter is removed. And so forth until the dialog is compressed and shows nothing STR: 1. Open Fennec 2. Tap the location bar to open the AwesomeScreen 3. Open the "Search With" dialog 4. Dismiss dialog and switch panes 5. Open the "Search With" dialog Notice the removed items.
Reporter | ||
Updated•14 years ago
|
Summary: "Search With" dialog keeps removing menu items on switch of AwesomeScreen panes → "Search With" dialog keeps removing menu items on switch of AwesomeScreen panes and or rotation
Reporter | ||
Comment 1•14 years ago
|
||
As well, one can see the menu items not properly fitting in the list by having the menu open and rotating the device through landscape and back to portrait
Assignee | ||
Comment 2•14 years ago
|
||
The patch tweak a bit the sizeToContent method of the MenuListHelperUI (I've mostly duplicate it from the ContextHelper's one) and also include a few css fixe for the preventing the first row of the menuhelper list to have round border if there is no box title (you can see this failure behavior in the open search list)
Assignee: nobody → 21
Attachment #470442 -
Flags: review?
Assignee | ||
Updated•14 years ago
|
Attachment #470442 -
Flags: review? → review?(mark.finkle)
Comment 4•14 years ago
|
||
Comment on attachment 470442 [details] [diff] [review] Patch >diff -r 30398110fbfe chrome/content/browser-ui.js >- preferredHeight += popup.children[i].getBoundingClientRect().height; >+ preferredHeight += popup.childNodes[i].getBoundingClientRect().height; Why this change? r+, but if we need the above change, should we add it to ContextHelper?
Attachment #470442 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 5•14 years ago
|
||
(In reply to comment #4) > Comment on attachment 470442 [details] [diff] [review] > Patch > > >diff -r 30398110fbfe chrome/content/browser-ui.js > > >- preferredHeight += popup.children[i].getBoundingClientRect().height; > >+ preferredHeight += popup.childNodes[i].getBoundingClientRect().height; > > Why this change? > > r+, but if we need the above change, should we add it to ContextHelper? We need it because we're not looking into the popup child anymore but we're still doing that for the context helper. http://hg.mozilla.org/mobile-browser/rev/bb790bfcba55
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 6•14 years ago
|
||
Verified fix on Mozilla/5.0 (Android; Linux armv7l; rv:2.0b5pre) Gecko/20100901 Firefox/4.0b5pre Fennec/2.0a1pre
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
tracking-fennec: ? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•