4 ms·

Why do we have shit like `enterkeyhint` but not some really simple things like <input type="slider" min="0" max="100" step="10" name="foo"> <input type

by dheera 5y ago

Why do we have shit like `enterkeyhint` but not some really simple things like <input type="slider" min="0" max="100" step="10" name="foo"> <input type="toggle" value="true" name="bar">

detaro 5y ago
We have the first, it's just not called "slider".
- throwanem 5y ago
  It's called "range", and I didn't know about it either: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range https://developer.mozilla.org/en-US/docs/Web/HTML/Element/in... And a "toggle" input is just a checkbox.
mahathu 5y ago
you mean range and checkbox inputs? (they both exist)
- dheera 5y ago
  range -- damn, nobody told me checkbox -- not a toggle, requires incredible pecking accuracy on mobile, non-hummingbirds cannot use
  - detaro 5y ago
    > requires incredible pecking accuracy on mobile, non-hummingbirds cannot use At least that part is easily solved: Assign a label to the checkbox, label is tap-able. nice large target. Styling it to look like a native toggle control is harder.
    - 6510 5y ago
      I remember that as the first time when using default styling of basic elements produced unusable results. I have to ask, when did it become my job to solve things like this?? Hidden check boxes with a check box in a label is not a nice elegant way of styling something at all. It's closer to an ugly hack. I find it an upsetting development given how well everything else was designed. It seems we are going to get more good ideas in unfinished form? The definition of a range is: "the area of variation between upper and lower limits on a particular scale." Why would the user only get to configure 1 of the 2? The definition of a slider is: a knob or lever that is moved horizontally or vertically to control a variable, such as the volume of a radio. enterkeyhint="next" conceptually a great idea. Sadly it doesn't do anything? I wanted an attribute that makes the button go to the "next field". Easily fixed by every developer individually a million+ times deep into the future.
      - throwanem 5y ago
        > I wanted an attribute that makes the button go to the "next field" What's wrong with the navigation controls provided by the browser for this purpose?
        6510 5y ago
        The up and down navigation controls provided by the browser work exactly the way we expect them to. We had a good thing going there. It does what it says on the tin. Its how I (and everyone else) like things. A stop button makes it stop. Scissors are to cut. The little floppy disk is to save. A play button makes it play. etc It seems so fundamental? How could anyone get this wrong? The user wants working buttons on their interface. Buttons that behave the way they expect. I think no one wants an enter key that looks like a "next" button. In case I'm mistaken about that they could simply add a different value domstring. >'enter' typically indicating inserting a new line. I have to inserts a new line at the cursor? >'done' typically meaning there is nothing more to input and the input method editor (IME) will be closed. I have to close it? >'go' typically meaning to take the user to the target of the text they typed. I have to submit the form? >'next' typically taking the user to the next field that will accept text. I have to move the cursor to the next field? >'previous' typically taking the user to the previous field that will accept text. I have to move the cursor to the previous field? >'search' typically taking the user to the results of searching for the text they have typed. I have to submit the form? >'send' typically delivering the text to its target. I have to submit the form? Maybe I'm missing something (I hope so)
  - throwanem 5y ago
    If a checkbox isn't a toggle, what then by you is a toggle?
    - dheera 5y ago
      Have you used a phone at all?
      - throwanem 5y ago
        Yes, every day since 2012 - I was a little late to the party, but managed to show up right around when it was really getting going. Unless the form is tiny and unzoomable, checkboxes have always seemed to work fine, no worse affected than any other web UI element by the essential imprecision of the interaction style.

by dheera 5y ago

Why do we have shit like `enterkeyhint` but not some really simple things like <input type="slider" min="0" max="100" step="10" name="foo"> <input type="toggle" value="true" name="bar">

detaro 5y ago

We have the first, it's just not called "slider".

throwanem 5y ago
It's called "range", and I didn't know about it either: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range https://developer.mozilla.org/en-US/docs/Web/HTML/Element/in... And a "toggle" input is just a checkbox.

mahathu 5y ago

you mean range and checkbox inputs? (they both exist)

dheera 5y ago
range -- damn, nobody told me checkbox -- not a toggle, requires incredible pecking accuracy on mobile, non-hummingbirds cannot use
- detaro 5y ago
  > requires incredible pecking accuracy on mobile, non-hummingbirds cannot use At least that part is easily solved: Assign a label to the checkbox, label is tap-able. nice large target. Styling it to look like a native toggle control is harder.
  - 6510 5y ago
    I remember that as the first time when using default styling of basic elements produced unusable results. I have to ask, when did it become my job to solve things like this?? Hidden check boxes with a check box in a label is not a nice elegant way of styling something at all. It's closer to an ugly hack. I find it an upsetting development given how well everything else was designed. It seems we are going to get more good ideas in unfinished form? The definition of a range is: "the area of variation between upper and lower limits on a particular scale." Why would the user only get to configure 1 of the 2? The definition of a slider is: a knob or lever that is moved horizontally or vertically to control a variable, such as the volume of a radio. enterkeyhint="next" conceptually a great idea. Sadly it doesn't do anything? I wanted an attribute that makes the button go to the "next field". Easily fixed by every developer individually a million+ times deep into the future.
    - throwanem 5y ago
      > I wanted an attribute that makes the button go to the "next field" What's wrong with the navigation controls provided by the browser for this purpose?
      - 6510 5y ago
        The up and down navigation controls provided by the browser work exactly the way we expect them to. We had a good thing going there. It does what it says on the tin. Its how I (and everyone else) like things. A stop button makes it stop. Scissors are to cut. The little floppy disk is to save. A play button makes it play. etc It seems so fundamental? How could anyone get this wrong? The user wants working buttons on their interface. Buttons that behave the way they expect. I think no one wants an enter key that looks like a "next" button. In case I'm mistaken about that they could simply add a different value domstring. >'enter' typically indicating inserting a new line. I have to inserts a new line at the cursor? >'done' typically meaning there is nothing more to input and the input method editor (IME) will be closed. I have to close it? >'go' typically meaning to take the user to the target of the text they typed. I have to submit the form? >'next' typically taking the user to the next field that will accept text. I have to move the cursor to the next field? >'previous' typically taking the user to the previous field that will accept text. I have to move the cursor to the previous field? >'search' typically taking the user to the results of searching for the text they have typed. I have to submit the form? >'send' typically delivering the text to its target. I have to submit the form? Maybe I'm missing something (I hope so)
- throwanem 5y ago
  If a checkbox isn't a toggle, what then by you is a toggle?
  - dheera 5y ago
    Have you used a phone at all?
    - throwanem 5y ago
      Yes, every day since 2012 - I was a little late to the party, but managed to show up right around when it was really getting going. Unless the form is tiny and unzoomable, checkboxes have always seemed to work fine, no worse affected than any other web UI element by the essential imprecision of the interaction style.