Open Bug 2057142 Opened 2 months ago Updated 1 day ago

Creating new tab no longer shows the keyboard with "Homepage as a new tab" is not enabled

Categories

(Firefox for Android :: Homepage, defect)

Firefox 155
All
Android
defect

Tracking

()

Tracking Status
firefox153 --- unaffected
firefox154 --- disabled
firefox155 --- disabled
firefox157 --- wontfix
firefox158 --- wontfix
firefox159 --- wontfix
firefox160 --- affected

People

(Reporter: klint, Unassigned, NeedInfo)

References

(Regression)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Android 12; Mobile; rv:155.0) Gecko/155.0 Firefox/155.0

Steps to reproduce:

Check that Homepage as a new page is NOT ENABLED
click on tab list icon
Click on +

Actual results:

The keyboard does not show up

Expected results:

The keyboard should have shown up

The Bugbug bot thinks this bug should belong to the 'Firefox for Android::Homepage' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → Homepage

:gl, looks like this is intended?

Flags: needinfo?(gl)
Keywords: regression
Regressed by: 2054518

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

This is still an issue. I'm hitting this many times a day and having to tap the URL bar manually every time is very frustrating.

Massive regression, I am not a big homepage user and diaable many components of it. I would prefer the keyboard always appear on a new tab as it always has.

Per BUG 2054518, this behavior is designed to be coupled with settings.enableHomepageTrendingRecentSearch but it does not seem to be, it occurs with all homepage configurations.

Actually, the behaviour of keyboard automated of the standard new TV button opening should be related to the presence or absence of the tab bar, because the + button in that bar does open the keyboard automatically.

...of the new tab bar...not TV!

Sorry.... New tab button....

The + button doesn't bring up the on-screen keyboard for me, and neither does opening a new tab or a new private tab in any other manner. I always have to manually press the address bar to get the keyboard to show up. This only started happening with the upgrade to version 157 on Android, but it's also broken in Firefox Beta and Firefox Nightly. Everything works as expected on version 156.0.1, however. I tested them all. Big usability regression in versions 157+

Duplicate of this bug: 2078374

this is no longer disabled as of bug 2067606, so marking flags

Duplicate of this bug: 2078201

This iż driving me nuts. It may seem tiny but for me Firefox is there most used app in my phone and I open it absurd number of times each day and in the overwhelming majority of case what I want is to search for something something having focus in the address bar and keyboard open is simply a MUST.

Recent change on 157 added this minute friction forcing me to explicitly tap on the address bar each time I open the Firefox effectively doubling the number of taps I have to made.

For my use case (home page with 8 speed dials only) not having keyboard doesn't make any sense. When it pop ups automatically I can still see just fine my 8 speed dials and can opt to navigate to any of those just fine (less likely).

Duplicate of this bug: 2078535
Severity: -- → S4

Won't fix? Why? At least add an option to get a keyboard on new tab, there are plenty of users that don't use the suggestions on the new tab. This is a reason for me to switch browsers tbh!

(In reply to dbuero from comment #15)

Won't fix? Why? At least add an option to get a keyboard on new tab, there are plenty of users that don't use the suggestions on the new tab.

I can't speak for the developers, but presumably it's simply too late to do that for version 159, which is due for release in a fortnight.

160 is still officially "affected" 😉

Duplicate of this bug: 2082666
Duplicate of this bug: 2077911
Duplicate of this bug: 2082752
You need to log in before you can comment on or make changes to this bug.