Open Bug 1677320 Opened 4 years ago Updated 1 year ago

layout.forms.input-type-search.enabled breaks text selection in search bar in toolbar

Categories

(Core :: Layout: Form Controls, defect, P3)

Firefox 84
defect

Tracking

()

People

(Reporter: gwarser, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

  • enable search bar in toolbar
  • enable layout.forms.input-type-search.enabled
  • restart Nightly
  • type one two in search bar
  • click on page
  • click in search bar between one and two
    • whole text is selected, cursor invisible
  • click again
    • nothing happens
  • try dragging to select word
    • nothing happens
  • tap on keyboard left/right arrow
    • selection disappears, cursor is moved to the beginning/end of text
  • tap on arrow again
    • nothing happens

20201114094625 on Manjaro KDE

Has STR: --- → yes
Regressed by: 558594
Version: unspecified → Firefox 84

:gwarser, if you think that's a regression, then could you try to find a regression range in using for example mozregression?

mozregression --good 78 --profile-persistence clone-first --pref security.sandbox.content.level:0 
22:29.04 INFO: Running autoland build built on 2020-07-27 14:10:44.756000, revision 955f2001
22:44.41 INFO: Launching /tmp/tmp3z_d4k37/firefox/firefox
22:44.41 INFO: Application command: /tmp/tmp3z_d4k37/firefox/firefox --allow-downgrade -profile /tmp/tmpmll77n9w.mozrunner
22:44.44 INFO: application_buildid: 20200727125512
22:44.44 INFO: application_changeset: 955f20019d71b001927385c180371016b7110b31
22:44.44 INFO: application_name: Firefox
22:44.44 INFO: application_repository: https://hg.mozilla.org/integration/autoland
22:44.44 INFO: application_version: 80.0a1
Was this integration build good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', 'back' or 'exit' and press Enter): good
23:02.14 INFO: Narrowed integration regression window from [fecbefc3, 6b085a98] (3 builds) to [955f2001, 6b085a98] (2 builds) (~1 steps left)
23:02.14 INFO: No more integration revisions, bisection finished.
23:02.14 INFO: Last good revision: 955f20019d71b001927385c180371016b7110b31
23:02.14 INFO: First bad revision: 6b085a98f2546c810bf23fded210019bd156f49d
23:02.14 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=955f20019d71b001927385c180371016b7110b31&tochange=6b085a98f2546c810bf23fded210019bd156f49d

Side note: it will be a lot easier if --pref option will be working correctly (probably bug 1246142 )

Has Regression Range: --- → yes

Thanks for running mozregression to confirm this is from bug 558594.

Tim, are you able to take a look?

Flags: needinfo?(ntim.bugs)

I can confirm this happens for me, thanks for filing!

I can't reproduce with data:text/html,<input type="search">, so probably just something conflicting in the searchbar click/focus event listener and <input type="search">.

Anyway, nobody is currently working on this feature, and it's still behind a preference, so I'll leave this for now.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(ntim.bugs)

The severity field is not set for this bug.
:jwatt, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jwatt)
Severity: -- → S3
Flags: needinfo?(jwatt)
Priority: -- → P3
Blocks: 1654288
You need to log in before you can comment on or make changes to this bug.