Closed tomclose closed 6 months ago
Name | Link |
---|---|
Latest commit | 8db047de66993af764c366d726662eae57e844b8 |
Latest deploy log | https://app.netlify.com/sites/stimulusreflex/deploys/660b43d698240a000806ba81 |
Deploy Preview | https://deploy-preview-692--stimulusreflex.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
@tomclose just wanted to tag you and mention that https://github.com/stimulusreflex/stimulus_reflex/pull/696 should be solving this issue! If you get a chance, I'd love to hear how it works for you! Thank you!
Type of PR (feature, enhancement, bug fix, etc.)
Description
Fixes the handling of
by making the following tradeoff:
Note: this is largely a revert of https://github.com/stimulusreflex/stimulus_reflex/commit/69cb070ec961dd52d34ec9a66a88f895686100c1
Fixes #652
Why should this be added
652 is a hard to debug and is easy to run into e.g. when building an autocomplete search box. The real fix for the bug involves an upstream change to Nokogiri, but it's unclear when that will happen. I don't know if this is a good tradeoff or not - just thought I'd propose it as an alternative to #674.
Checklist