Dmitry Zarva

I'm also experiencing some critical issues in Chrome 105 that I've never seen before 105 release, using immutable.js based version of SlateJS editor (`[email protected]` + `[email protected]`) https://codesandbox.io/s/cfdps 1. Try to...

@beaugunderson OMG! I can't believe that all the issues in Chrome 105 described in my previous comment here were because of [style](https://github.com/ianstormtaylor/slate/blob/slate%400.47.4/packages/slate-react/src/components/content.js#L510) `WebkitUserModify: 'read-write-plaintext-only'` on `contentEditable` container. After some deep...

> it's related to #5108 no? https://github.com/ianstormtaylor/slate/issues/5108#issuecomment-1235137908

> > @beaugunderson > > > > > > OMG! I can't believe that all the issues in Chrome 105 described in my previous comment here were because of [style](https://github.com/ianstormtaylor/slate/blob/slate%400.47.4/packages/slate-react/src/components/content.js#L510)...

@ThomasEsseul Why some another workaround needed? Didn't this help you? - https://github.com/ianstormtaylor/slate/issues/5110#issuecomment-1235150979 I have no issues in Chrome 105 using Slate 0.47.8 after I removed `WebkitUserModify: 'read-write-plaintext-only'` completely. But I...

`HAS_INPUT_EVENTS_LEVEL_2 === true` in Chrome 105, coz `'onbeforeinput' in element === true`, so there is no any issue with level2 input events detection. There is one another issue, please check...

@Titozzz , could you please take a look if you have some time? 🙏

still searching for solutions

> Just don't use new architecture. Peace. Thanks, but that's not a solution.

still searching for solutions