Reputation: 5591
So, I have two contenteditable divs nested inside of another:
<div class="top" contenteditable="true">
<div class="nested" contenteditable="true">This</div>
</div>
Here is Fiddle.
When it is focused, nested
should be focused but using console.log(document.activeElement);
it shows that the top
is focused and it doesn't recognize the nested
div.
In a case where content is being edited, I need to recognize nested
div element instead of the top
element.
How would I achieve this? Any help will be much appreciated.
Upvotes: 6
Views: 3115
Reputation: 721
For nested contentEditable elements, focus shall be only triggered in the top ancestor. You could use selection to get the closest element where the caret is right in:
function getCEOfCaret(){
const selection = window.getSelection()
const range = selection.getRangeAt(0)
const start = range.startContainer;
let startElement;
if(start.nodeType === 1) startElement = start;
else startElement = start.parentElement;
return startElement.closest('[contenteditable="true"]')
}
console.log(getCEOfCaret())
Upvotes: 0
Reputation: 3734
Give tabindex=-1
to the nested div, than can be focused:
.nested {
display: inline;
background-color: #eef;
}
<div class="top" contenteditable="true">
Editable div <div class="nested" tabindex=-1>Nested div</div>
</div>
Notes:
contenteditable
is inherited, so there is no need to specify it again.keydown
listener, range
and selection
.Upvotes: 0
Reputation: 74420
The way [contenteditable]
elements are handled by browser made any nested [contenteditable]
not handling any event, the editing host is the former editable parent. See spec:
If an element is editable and its parent element is not, or if an element is editable and it has no parent element, then the element is an editing host. Editable elements can be nested. User agents must make editing hosts focusable (which typically means they enter the tab order). An editing host can contain non-editable sections, these are handled as described below. An editing host can contain non-editable sections that contain further editing hosts.
Now as a workaround, you could make focused nested editable element the hosting host by setting any of its editable parent temporaly not editable. See e.g:
$('div.top [contenteditable]').on('focusin focusout', function(e) {
$(this).parents('[contenteditable]').prop('contenteditable', e.type === "focusout");
});
Upvotes: 1