Jim Fisher

~~It looks like this is the only substantial change: https://github.com/ianstormtaylor/slate/pull/4889~~

Temporary workaround: instead of doing nothing, make an invisible change. Example: https://codesandbox.io/s/workaround-for-slatejs-bug-inserttext-should-do-nothing-if-it-returns-wzc647?file=/index.js

~~I don't fully understand what https://github.com/ianstormtaylor/slate/pull/4889 is doing. I tried reverting that change, but the bug persists. Perhaps it is not the source of this bug, or there are further...

Okay, it gets weirder ... on Chrome, this breaks between [email protected] and [email protected]. But on Firefox, it breaks between [email protected] and [email protected]! Which again suggests that maybe https://github.com/ianstormtaylor/slate/pull/4889 is not...

The diff is much larger for the Firefox breakage: https://github.com/ianstormtaylor/slate/compare/slate-react%400.65.3...slate-react%400.66.0. Although, like the diff that breaks Chrome, it makes changes to `Slate.Transforms.setNodes`.

Aha, thanks @BitPhinix! So https://github.com/ianstormtaylor/slate/pull/4889 is nothing to do with this; the cause was https://github.com/ianstormtaylor/slate/pull/4883. With [email protected], my modern Chrome was being identified as "legacy", in which case Slate does...

To confirm this, I downloaded Chrome 99, as it is not affected by the Chrome regex thing, which was masking the real bug. This time, Chrome v99 agrees with Firefox:...

slate-react 0.66.0 introduced this "native event" thing in https://github.com/ianstormtaylor/slate/pull/3888. So the bug has existed ever since this was first added.

I can reproduce - this recently started happening to me. AltTab 6.64.0 macOS 14.1.2

I did some previous work on macOS window management. Here's an example of an "odd" window: ```swift let panel:NSPanel = NSPanel( styleMask: [ NSWindow.StyleMask.nonactivatingPanel, ], ) panel.collectionBehavior = [ NSWindow.CollectionBehavior.canJoinAllSpaces,...