Closed Bug 1172347 Opened 9 years ago Closed 9 years ago

Homescreen search widget not usable with physical keyboard

Categories

(Firefox for Android Graveyard :: Search Activity, defect)

38 Branch
defect
Not set
normal

Tracking

(fennec38+)

RESOLVED DUPLICATE of bug 1158906
Tracking Status
fennec 38+ ---

People

(Reporter: persona, Assigned: sebastian)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150511103818

Steps to reproduce:

I'm using Firefox for Android 38.0.5 on a Samsung Galaxy S Relay 4G with Android 4.1.2. I have added the "Firefox Search" widget to my homescreen. 

1. Slide open the physical keyboard. 
2. Press the search section of the "Firefox Search" widget.
3. Type some search query.
4. Press enter.


Actual results:

Nothing happens (except the search suggestions disappear).



Expected results:

The search should have activate with the typed-in query, as if the "search" button on the software keyboard had been pressed. I have not found another key or on-screen button that would activate the search.
Status: UNCONFIRMED → NEW
Ever confirmed: true
tracking-fennec: --- → ?
Assignee: nobody → margaret.leibovic
tracking-fennec: ? → 38+
Is this a new problem that started when you updated to Firefox 38?
Flags: needinfo?(persona)
I don't know, I used to use the standard Google search bar until I found out there was a Firefox one.
Flags: needinfo?(persona)
kbrosnan, do we have one of these devices somewhere? Is there one in SF?
Flags: needinfo?(kbrosnan)
I need to be at Google SF tomorrow, I could drop one off at Mozilla while I'm there for testing. I'll need it back at some point.
I can confirm that this is reproducible with a Nexus 9 and the keyboard folio. I'll try to fix that.
Assignee: margaret.leibovic → s.kaspari
Status: NEW → ASSIGNED
Flags: needinfo?(kbrosnan)
I would suggest a Bluetooth keyboard. There are not many devices any more with a physical keyboard.
This has already been fixed in bug 1158906:
http://hg.mozilla.org/mozilla-central/rev/3f2af35fb884

And I can confirm that this bug is only reproducible with Firefox 38.0 and Beta (39.0) with my Nexus 9. The enter key is working with my own Fennec and Nightly builds.

@Jethro: Can you confirm that this is fixed on your phone too - using a Nightly build[1]?

[1]: https://nightly.mozilla.org/ or direct download: https://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-api-11/fennec-41.0a1.multi.android-arm.apk
Flags: needinfo?(persona)
Seems to work, thanks for the fix.

However, sometimes if I type and press enter really fast, the query goes through and might come back, but then the search suggestions list pops up over the results.
Flags: needinfo?(persona)
(In reply to Jethro Beekman from comment #8)
> Seems to work, thanks for the fix.

Thank your for testing!

> However, sometimes if I type and press enter really fast, the query goes
> through and might come back, but then the search suggestions list pops up
> over the results.

That's interesting. I tried to reproduce this but couldn't. Maybe it depends on how fast we can load the suggestions? Can you open another bug for this? Maybe attach a screenshot if possible.


@mfinkle: With "tracking-fennec: 38+" flag set, do we need to uplift the patch or can I close this bug as duplicate of bug 1158906?
Flags: needinfo?(mark.finkle)
(In reply to :Sebastian Kaspari from comment #9)

> @mfinkle: With "tracking-fennec: 38+" flag set, do we need to uplift the
> patch or can I close this bug as duplicate of bug 1158906?

I'll dupe this bug to bug 1158906 and request uplift to 39, if possible.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(mark.finkle)
Resolution: --- → DUPLICATE
> That's interesting. I tried to reproduce this but couldn't. Maybe it depends on 
> how fast we can load the suggestions? Can you open another bug for this? Maybe 
> attach a screenshot if possible.

https://bugzilla.mozilla.org/show_bug.cgi?id=1176418
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.