Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.As of #731724: Convert comment settings into a field to make them work with CMI and non-node entities, comment settings are a field. When rendered, you get to see the actual comments plus possibly the comment form. However, to Edit module, this is just another field; it has no way of knowing that this in fact not a field with actual editable content. So it marks the stuff CommentDefaultFormatter outputs as in-place, by setting a data-edit-field-id attribute on it.
Consequently, there is a bizarre blue bar (which is actually the "comment field" being marked as in-place editable) at the bottom of the page when in-place editing, that clearly makes in-place editing look broken:
The solution is to set edit.editor = "disabled" in CommentDefaultFormatter's annotation: that tells Edit that this field formatter does not support in-place editing at all. Result:
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | disable_in_place_editing_comment_field-2136895-1.patch | 730 bytes | wim leers |
| after.png | 48.79 KB | wim leers | |
| before.png | 48.81 KB | wim leers |
Comments
Comment #1
wim leersEt voila. Très simple.
Comment #2
jessebeach commentedNice! A simple patch that keeps the comment field from being processed for in place edit.
This patch made me look again at why we are hiding the comments during in place editing. I decided to see if we could keep them visible. The reason they are hidden is due to the placement algorithm of the Entity Toolbar, so I updated this #2137005: Don't hide comments during in-place editing of an Article; position the entity toolbar more intelligently.
Comment #3
larowlanThanks, great catch - +1
Comment #4
webchickNice, I saw this pop up in demos fairly recently and wasn't sure where it was coming from.
Committed and pushed to 8.x. Thanks!
Comment #5
wim leers