• In Jupyter notebooks (and, theoretically, other rich content) we find an inner <td /> before finding the content <td />, preventing context menus from working.

• In Firefox, multi-line selections don't generate a context menu properly.
• Clicking the "New Inline Comment" action disables the oncopy behavior onmousedown but doesn't take the action until onclick. This creates a flash of selected content which spans both sides of the change and looks odd.
• Context selection doesn't activate in unified mode, maybe because data-copy stuff is being used to identify content cells.

• When you create an inline, do nothing, then click "Cancel", inlines briefly count themselves in the paths panel.

I have a patch which allows you to edit published inlines. It "works", but it causes a ton of weird side effects when you perform an edit.

Inline stuff:

• Also restrict the list for changes with no candidate engines.

Probably kicking this, but:

See PHI1703. The document engine the original comment was made on should be persisted, so email can do something better than dumping unrelated lines of text into the body.

The SSH username change wasn't sufficient because there's a hard-coded piece of logic to select the username by instance name:

If pre-commit can not mutate the commit

The preview section underneath the comment area doesn't mark "editing" inlines in any special way.