Chrome 105 breaks slate 0.27.x
See original GitHub issueDescription Our application (an electronic health record) uses slate in production; versions:
"slate": "0.27.4",
"slate-auto-replace": "0.8.1",
"slate-react": "0.7.2",
The update to Chrome 105 now rolling out breaks the ability for slate to find a DOM point, it looks like.
In the above screenshot you can see that leaf will be null as end
is zero and point.offset
is 2, meaning the condition of end >= point.offset
will never be satisfied.
I realize we’re on an old version of slate but if there’s a known fix for Chrome 105 issues or a link to crbug for whatever the regression is there we would be very grateful.
Recording Will follow up with a GIF.
Environment
- Slate Version: 0.27.4
- Operating System: macOS
- Browser: Chrome 105
Issue Analytics
- State:
- Created a year ago
- Reactions:8
- Comments:36 (9 by maintainers)
Top Results From Across the Web
New in Chrome 105 - Chrome Developers
Chrome 105 is rolling out now. Container queries and :has() are a match made in responsive heaven. The new Sanitizer API provides a...
Read more >Google Chrome - Download the Fast, Secure Browser from ...
Get more done with the new Google Chrome. A more simple, secure, and faster web browser than ever, with Google's smarts built-in. Download...
Read more >Terry Rozier NBA Stats & News - Rotowire
Dan Bruno breaks down Wednesday's slate of games and likes De'Aaron Fox against a Lakers team that gives up the sixth most points...
Read more >Chrome Update 105.0.5195.102 break something? - Issues
Chrome v105 may break HOT old version when “.ht_clone_top .wtHolder” has a horizontal scrollbar and the value of overflow of style of ...
Read more >Fix Chrome update problems & failed updates - Google Support
Chrome doesn't work with the following older platforms: Windows XP; Windows Vista; Mac OS X 10.6–10.12. Use a recent operating system to make...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@beaugunderson
OMG! I can’t believe that all the issues in Chrome 105 described in my previous comment here were because of style
WebkitUserModify: 'read-write-plaintext-only'
oncontentEditable
container.After some deep investigation, I realized that
event.getTargetRanges()
returns an empty array inonBeforeInput
handler inafter
plugin when thatWebkitUserModify
style applied. In this caseonBeforeInput
handler returns and does nothing, so that you can seeonInput
event handler works instead as a fallback that leads to some unexpected behaviour in my cases.Please check it out for your case - it might be the root of the issue you are experiencing.
@ThomasEsseul
Yes, we meet the exact same problem with ê, â … characters.
@Slapbox
We applied the
-webkit-user-modify
fix but still have problems with accented characters.Does anyone knows a fix around this particular issue?