Yes, indeed I've *just* confirmed that these "crashes" on facebook.com and draftjs.org (bug 1739489) are fixed with an webcompat site intervention which maps `beforeinput` to `textInput` (and also `window.TextEvent` to `window.InputEvent`). It may also be triggering Facebook to provide a different user-experience for the editor, though I don't use Facebook myself so I cannot be 100% sure. I'm also not sure if this will fix anything else, but it doesn't seem to be breaking anything obvious in my initial tests, so I will propose a patch here for both bugs, so we can dogfood it a little and determine if it's the way we want to go (and whether we want to limit it to nightly only or OSX only for the foreseeable future).
Bug 1739489 Comment 29 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yes, indeed I've *just* confirmed that these "crashes" on facebook.com and draftjs.org (bug 1739489) are fixed with an webcompat site intervention which maps `beforeinput` to `textInput` (and also `window.TextEvent` to `window.InputEvent`). It may also be triggering Facebook to provide a different user-experience for the editor, though I don't use Facebook myself so I cannot be 100% sure. I'm also not sure if this will fix anything else, but it doesn't seem to be breaking anything obvious in my initial tests, so I will propose a patch on the other bug, so we can dogfood it a little and determine if it's the way we want to go (and whether we want to limit it to nightly only or OSX only for the foreseeable future).
Yes, indeed I've *just* confirmed that these "crashes" on facebook.com and draftjs.org are fixed with an webcompat site intervention which maps `beforeinput` to `textInput` (and also `window.TextEvent` to `window.InputEvent`). It may also be triggering Facebook to provide a different user-experience for the editor, though I don't use Facebook myself so I cannot be 100% sure. I'm also not sure if this will fix anything else, but it doesn't seem to be breaking anything obvious in my initial tests, so I will propose a patch, so we can dogfood it a little and determine if it's the way we want to go (and whether we want to limit it to nightly only or OSX only for the foreseeable future).