Closed Bug 640754 Opened 13 years ago Closed 13 years ago

Resizing and panning occurs during the times when the VKB is opened/closed causing a visual performance decline in VKB appearance/disappearance

Categories

(Firefox for Android Graveyard :: General, defect, P1)

ARM
Android
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 636792

People

(Reporter: nhirata, Unassigned)

Details

(Keywords: regression, Whiteboard: performance, [vkb])

Mozilla/5.0 (Android; Linux armv71; rv2.0b13pre) Gecko/20110310 Firefox/4.0b13pre Fennec/4.0b6pre
Device: Droid 2 
OS: Android 2.2

1. go to www.google.com
2. click in the text field
3. observe the keyboard and the words of the html
4. hit the system back button
5. observe

Expected: you should not be able to see the black area of the VKB screen.

Actual: you can see a performance issue with the VKB open and close due to the resizing and panning operations during the time the VKB is opened.  This does not occur in the stock browser.

See videos:
stock web browser: http://www.youtube.com/watch?v=1hGURUq4UAk
fennec web browser: http://www.youtube.com/watch?v=kjJa81F6pIo

Note:
1. tried using various VKB with same effect.
2. there is a different in the VKB appearance in landscape mode with certain VKBs when comparing the stock web browser to fennec.
3. Clicking on the text field is hard when the field is small in fennec

Side note:
1. bug based on discussion about this issue which was brought up by Aakashd and talked through with mfinkle and nhirata
2. Dismissing via tapping on white space versus tapping the system back different is different on the stock web browser (dismissing via the white space will cause the field to scroll up next time it is clicked.  not sure if that's intentional or not)
Keywords: regression
tracking-fennec: --- → ?
Priority: -- → P1
Whiteboard: performance, [vkb]
tracking-fennec: ? → 2.0next+
tracking-fennec: 2.0next+ → 6+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
tracking-fennec: 6+ → ---
You need to log in before you can comment on or make changes to this bug.