4 ms·

I haven’t tested myself, but according to MDN the select event on <input> elements should be supported by Safari? https://developer.mozilla.org/en-US/docs/Web/

I haven’t tested myself, but according to MDN the select event on <input> elements should be supported by Safari? https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/select_event https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputEl...

kccqzy 2y ago
The MDN page you linked to includes a nice selection logger example. It just doesn't work on my Safari (iOS).
- chrismorgan 2y ago
  And does an equivalent in React work? Because I don't believe React does any of the papering-over you describe. My understanding (as a non-user) is that React does, logically, essentially nothing special around event handling.
  - kccqzy 2y ago
    I don't remember off the top of my head whether this specific example works in React as I'm not next to a computer. But I remember reading React source code and finding a whole lot of code to handle the select event. (Just found it by doing a GitHub code search on my phone https://github.com/facebook/react/blob/7c8e5e7ab8bb63de911637892392c5efd8ce1d0f/packages/react-dom-bindings/src/events/plugins/SelectEventPlugin.js#L137 https://github.com/facebook/react/blob/7c8e5e7ab8bb63de91163...) In general React has its own event handling code. For one in React the user doesn't even deal with the browser native DOM events but React synthetic events. React also readily creates brand new synthetic events from other browser events. React also sometimes gives different names or behaviors to browser events; the most famous example is that the React onChange event is roughly equivalent to the browser onInput event, but absolutely different from the browser onChange event.
    - chrismorgan 2y ago
      Good to know, thanks. I knew it made synthetic events, but thought it was all still 1:1. I see I was completely wrong. I gotta say, yuck. Don't like it, wish they'd taken a more polyfill-like approach.
      - Izkata 2y ago
        IIRC they do that to deal with browser differences and be consistent with things like event bubbling. Probably other benefits as well but that's the one I'm fairly sure I remember from years ago.
  - fiddlerwoaroof 2y ago
    There are a couple of edge cases I forget at the moment where react event handlers intentionally behave differently from the DOM handlers with the same name.

kccqzy 2y ago

The MDN page you linked to includes a nice selection logger example. It just doesn't work on my Safari (iOS).

chrismorgan 2y ago
And does an equivalent in React work? Because I don't believe React does any of the papering-over you describe. My understanding (as a non-user) is that React does, logically, essentially nothing special around event handling.
- kccqzy 2y ago
  I don't remember off the top of my head whether this specific example works in React as I'm not next to a computer. But I remember reading React source code and finding a whole lot of code to handle the select event. (Just found it by doing a GitHub code search on my phone https://github.com/facebook/react/blob/7c8e5e7ab8bb63de911637892392c5efd8ce1d0f/packages/react-dom-bindings/src/events/plugins/SelectEventPlugin.js#L137 https://github.com/facebook/react/blob/7c8e5e7ab8bb63de91163...) In general React has its own event handling code. For one in React the user doesn't even deal with the browser native DOM events but React synthetic events. React also readily creates brand new synthetic events from other browser events. React also sometimes gives different names or behaviors to browser events; the most famous example is that the React onChange event is roughly equivalent to the browser onInput event, but absolutely different from the browser onChange event.
  - chrismorgan 2y ago
    Good to know, thanks. I knew it made synthetic events, but thought it was all still 1:1. I see I was completely wrong. I gotta say, yuck. Don't like it, wish they'd taken a more polyfill-like approach.
    - Izkata 2y ago
      IIRC they do that to deal with browser differences and be consistent with things like event bubbling. Probably other benefits as well but that's the one I'm fairly sure I remember from years ago.
- fiddlerwoaroof 2y ago
  There are a couple of edge cases I forget at the moment where react event handlers intentionally behave differently from the DOM handlers with the same name.