Inline Edit assumes there will always be a container element wrapping the display text. For simple scenarios, this is an unnecessary burden for the developer.
Description
At the moment, InlineEdit requires the display text to be contained in an element that is inside the component container. This is required, because the text needs to be hidden when switching into edit mode.
However, for some simple cases, this might be a burden on the developer, as it would be unnatural in the basic markup. For example, making the cells in a table editable: usually, the text in a cell is just in the <td> element, NOT inside an element inside the <td> element: ... <td>Bootsy Collins</td> ... In this example, the <td> element cannot be used as the container of an Inline Edit.
We should consider detecting this kind of case, and if necessary wrapping the text in a span ourselves.
At the moment, InlineEdit requires the display text to be contained in an element that is inside the component container. This is required, because the text needs to be hidden when switching into edit mode.
However, for some simple cases, this might be a burden on the developer, as it would be unnatural in the basic markup. For example, making the cells in a table editable: usually, the text in a cell is just in the <td> element, NOT inside an element inside the <td> element:
...
<td>Bootsy Collins</td>
...
In this example, the <td> element cannot be used as the container of an Inline Edit.
We should consider detecting this kind of case, and if necessary wrapping the text in a span ourselves.