Closed
Bug 799402
Opened 12 years ago
Closed 12 years ago
Panning sometimes accidentally focuses the URL bar
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-basecamp:+)
RESOLVED
WORKSFORME
blocking-basecamp | + |
People
(Reporter: cjones, Assigned: cyu)
References
Details
Attachments
(1 file)
106.63 KB,
image/png
|
Details |
I don't have good STR yet, but it's pretty easy to reproduce in general browsing.
When this happens, the VKB pops up unexpectedly. It took me a bit to figure out how to make it go away (re-focus URL bar, cancel input). I don't think the average user would figure out how to dismiss it.
Updated•12 years ago
|
blocking-basecamp: ? → +
Updated•12 years ago
|
Keywords: testcase-wanted
Comment 1•12 years ago
|
||
CC+ Benoit since this is filed against gfx layers.
Chris, can you try to find a reliable way to reproduce this?
Updated•12 years ago
|
Component: Graphics: Layers → General
Product: Core → Boot2Gecko
Question: do you see the Awesome page as well as the VKB? Or just the VKB?
Because if you see the awesome page as well, then you hit the url bar...
Otherwise it may be that you hit a field on the webpage itself and that's pulling up the VKB which is similar to bug 797586
Reporter | ||
Comment 4•12 years ago
|
||
I don't believe I'll able to produce better STR than "pan around quickly". I still see this in recent builds.
I'm about 95% sure this problem is us focusing the URL bar's input field somehow during its hide animation. Putting a pointer-events:none on the input's container when the animation starts is a possible workaround.
This is likely to the AsyncPanZoomController, right?
Reporter | ||
Comment 6•12 years ago
|
||
It's possible that code supporting apzc is contributing to this, yeah.
Hrm, I keep pulling the notifications down rather than getting focus on the url bar. Can you try typing next time in the keyboard to see if typing can occur in the URL bar when this occurs please? I can't seem to get it to repro yet.
Assignee | ||
Comment 8•12 years ago
|
||
It's easier to trigger this bug with the slower debug build. When this happens the VKB will still be seen on the home screen as attached screenshot. I will take a look since it's very reproducible on my device.
Assignee: nobody → cyu
Ah! That would explain it... I'm not using a debug build. Thanks cyu!
Keywords: qawanted,
testcase-wanted
Assignee | ||
Comment 10•12 years ago
|
||
I can no longer reproduce this bug in recent builds, even in non-optimized debug builds. Maybe it's fixed in other bugs.
Comment 11•12 years ago
|
||
Chris, do you agree this is gone now and can be closed?
Flags: needinfo?(jones.chris.g)
Comment 12•12 years ago
|
||
Chris, do you agree this is gone now and can be closed?
Reporter | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(jones.chris.g)
You need to log in
before you can comment on or make changes to this bug.
Description
•