Open Bug 1622947 Opened 4 years ago Updated 9 months ago

input type="number" with datalist, repeat up/down keys increases or decreases values only once

Categories

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

76 Branch
Desktop
Windows
defect

Tracking

()

Tracking Status
thunderbird_esr68 --- unaffected
firefox-esr68 --- unaffected
firefox74 --- unaffected
firefox75 --- unaffected
firefox76 --- wontfix
firefox77 --- fix-optional

People

(Reporter: alice0775, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: nightly-community, regression, Whiteboard: [layout:backlog:quality])

After landing Bug 1620778,

Str:

  1. Open http://jsbin.com/quluwijohe/1/edit
  2. Focus the field
  3. Repeat keypress ↑ or ↓

Actual results:

Strange behavior.
The value increases or decreases only once.

Expected results:
The value increases or decreases with each keypress.

Hmmm, fantastic fail on my side, I was pretty sure I had tested that case...

Thanks for reporting as always Alice, you're amazing.

Assignee: nobody → emilio
Flags: needinfo?(emilio)
Priority: -- → P2

Huh, I can't repro on Linux... Is this on Windows?

Flags: needinfo?(emilio) → needinfo?(alice0775)

Or, does the autocomplete popup show up once after you press it? If so it's a kinda weird interaction because it shows up when there are results that match the input value, but it's not clear what would be the right interaction there...

Maybe we could suppress the popup if there's a repeating keypress somehow.

(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)

Huh, I can't repro on Linux... Is this on Windows?

Yes, windows.

Flags: needinfo?(alice0775)
OS: All → Windows

What about the question in comment 3? Thank you.

(In reply to Emilio Cobos Álvarez (:emilio) from comment #3)

Or, does the autocomplete popup show up once after you press it?

Yes.

If so it's a kinda weird interaction because it shows up when there are results that match the input value,
but it's not clear what would be the right interaction there...

Maybe we could suppress the popup if there's a repeating keypress somehow.

Yes, but it is complicated. It needs to organize how to interact with the keyboard...

Hi Emilio - are you planning on working on this for 76 during the beta?

Flags: needinfo?(emilio)

I thought this was a somewhat more serious issue at first, I don't think it's a P2.

This probably needs some UX input or something.

Assignee: emilio → nobody
Flags: needinfo?(emilio)
Priority: P2 → P3

Changing the priority to p2 as the bug is tracked by a release manager for the current nightly.
See What Do You Triage for more information

Priority: P3 → P2

It does feel broken, and yes I think we need some UX input. Doesn't seem like there is much standard behavior. Trying this on Mac in both Firefox and Chrome:

  1. On initial focus and pressing ↓: For Firefox, I get a negative value, no popup. On Chrome the popup appears on initial focus and I select a value from the datalist. Chrome feels better in this case.
  2. On initial focus and pressing ↑: For Firefox, the popup appears after pressing ↑ and I select a value. On Chrome the popup appears on initial focus but ↑ does nothing (presumably because the popup is below). Firefox feels better in this case.
  3. After selecting an item from the data list and pressing ↑ or ↓ multiple times: For Firefox, it feels broken at this point. You can't nudge values up or down, but the popup appears. On Chrome it also feels broken; you can nudge values up and down, but the popup will no longer appear. Chrome seems better, but both feel broken for different reasons.

Stephen do you know who could provide input on how this should work?

Flags: needinfo?(shorlander)
Summary: input type="number", Repeat up/down keys increase or decrease values only once → input type="number" with datalist, repeat up/down keys increases or decreases values only once

Ryan: Based on comment 8 do you think we should keep tracking? I'd prioritize this as P3 and not track it. It's kind of wonky in Firefox and Chrome for different reasons.

If anything we should simply fix it so that the popup appears on first ↑ or ↓ (or on focus) but we don't increment or decrement the value in the field while the popup is open.

Flags: needinfo?(ryanvm)

Sounds reasonable.

Flags: needinfo?(ryanvm)

(In reply to Sean Voisen (:svoisen) from comment #11)

Ryan: Based on comment 8 do you think we should keep tracking? I'd prioritize this as P3 and not track it. It's kind of wonky in Firefox and Chrome for different reasons.

If anything we should simply fix it so that the popup appears on first ↑ or ↓ (or on focus) but we don't increment or decrement the value in the field while the popup is open.

I just set the priority accordingly.

Priority: P2 → P3
Severity: normal → S3
Whiteboard: [layout:backlog:quality]
Blocks: input-list
Has Regression Range: --- → yes

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.

Flags: needinfo?(stephen)
You need to log in before you can comment on or make changes to this bug.