Comment by uxcolumbo 9 hours ago Can you provide more details about the issues? 2 comments uxcolumbo Reply jwr 3 hours ago Not really, because I no longer remember. I only remember bugs and frustration. But I looked at my code quickly and found this:;; Let's render radio buttons ourselves. Because of bugs in React and Chrome, radio buttons mysteriously stop working.;; https://stackoverflow.com/questions/48423061/radio-buttons-n...;; https://github.com/facebook/react/issues/3446followed by my own implementation of radio buttons, followed by:;; Original implementation, to be used when radio buttons actually work:followed by an implementation using an input of type radio, commented out. paulhebert 1 hour ago Reading through the threads that sounds like a React bug not a browser bug
jwr 3 hours ago Not really, because I no longer remember. I only remember bugs and frustration. But I looked at my code quickly and found this:;; Let's render radio buttons ourselves. Because of bugs in React and Chrome, radio buttons mysteriously stop working.;; https://stackoverflow.com/questions/48423061/radio-buttons-n...;; https://github.com/facebook/react/issues/3446followed by my own implementation of radio buttons, followed by:;; Original implementation, to be used when radio buttons actually work:followed by an implementation using an input of type radio, commented out. paulhebert 1 hour ago Reading through the threads that sounds like a React bug not a browser bug
Not really, because I no longer remember. I only remember bugs and frustration. But I looked at my code quickly and found this:
;; Let's render radio buttons ourselves. Because of bugs in React and Chrome, radio buttons mysteriously stop working.
;; https://stackoverflow.com/questions/48423061/radio-buttons-n...
;; https://github.com/facebook/react/issues/3446
followed by my own implementation of radio buttons, followed by:
;; Original implementation, to be used when radio buttons actually work:
followed by an implementation using an input of type radio, commented out.
Reading through the threads that sounds like a React bug not a browser bug