Form input selection arrows are rendered partially off screen after switching from landscape to portrait mode 1) Go to http://aaronmt.com/?p=4492 2) Flip to landscape mode 3) Select one of the input boxes (no need to type) 4) Hit the back button to dismiss the keyboard 5) Flip to portrait mode and notice the arrows are rendered partially off screen
unable to reproduce on a Nexus S, 5/16 nightly build. Can you report which phone you're using, and also include a screenshot?
Rooted Evo 4G with cyanogen mod 7. Try loading the page in landscape mode first.
(In reply to comment #1) > unable to reproduce on a Nexus S, 5/16 nightly build. Can you report which > phone you're using, and also include a screenshot? I can reproduce with Kurt'z suggestion in comment #2 (load the page in landscape, and rotate to portrait after tap in the field)
Assignee: nobody → 21
tracking-fennec: ? → 6+
I can't reproduce on a nexus one even with the suggestion of #c2. I should do something wrong.
Kurt, are you still able to reproduce on the latest nightly? i filed bug 657836 yesterday which may now affect this bug.
I can still reproduce on my N1 Vivien, with 05/18. Try loading in landscape, tap the comment field, dismiss the keyboard, and then rotate to portrait
(In reply to comment #6) > I can still reproduce on my N1 Vivien, with 05/18. > > Try loading in landscape, tap the comment field, dismiss the keyboard, and > then rotate to portrait Really I can't. But maybe I'm on the wrong page because I don't have any "comment" field on that page, onyl a search field since the page is "Not Found" for me.
Also I don't think this bug should block FF6 since the arrows are going to be hidden on Android once bug 636339 will land.
(In reply to comment #8) > Also I don't think this bug should block FF6 since the arrows are going to > be hidden on Android once bug 636339 will land. It will certainly be a low priority and it won't block Fx6. The resize/positioning issue in this bug might be impacting other code too. So if we can figure out the cause, it would make our code more robust. (tracking-fennec != blocking-fennec)
There is a race between the resizeHandler calls of chrome/content/browser.js and the resize handler of the content popup helper code.
Attachment #533660 - Flags: review?(mark.finkle)
Comment on attachment 533660 [details] [diff] [review] Patch It's good to know this could happen
Attachment #533660 - Flags: review?(mark.finkle) → review+
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Due to the fact that form assistant feature was dropped , I will mark this bug as verified fixed. Build Id: Mozilla /5.0 (Android;Linux armv7l;rv:6.0a1) Gecko/20110523 Firefox/6.0a1 Fennec/6.0a1 Build ID: Mozilla /5.0 (Android;Linux armv7l;rv:5.0a2) Gecko/20110522 Firefox/5.0a2 Fennec/5.0a2 Device: HTC Desire Z (Android 2.2)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.