facebook.com and related properties are currently unsupported

[jessepollak]

Currently, all Facebook properties are unsupported. These include:

• facebook.com
• messenger.com

Here's what we know so far. Facebook uses contenteditable fields for all user input. I believe these contenteditable fields are backed by React and use the virtual DOM. This means that the normal way we handle contenteditable fields (with the browser's built in Range functionality) do not work. We've tried:

• replacing innerHTML for the whole contenteditable field
  • this doesn't work at all — the field becomes completely inaccessible

[cliffordp]

I was typing a Facebook comment and wrote ... unofficial / unsupported ... and it blew away my entire paragraph of text and somehow Cmd+Z didn't undo! 👎

Just something to be aware of.

[ctsstc]

I keep trying to type stuff with / in it on FB and it jumps to somewhere, deletes text, and jumbles things up. For now can we hard code a blacklist in for these known sites so it doesn't show up? Or is there some flag/attribute to avoid with these known React fields?

The nice to have would probably be a configurable blacklist, maybe pre-populated.

It's a fairly large nuisance since you can't even delete the / character, everytime you go back to it, it pops the popup and then as soon as key comes through it goes to the start of the current paragraph.