summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic
diff options
context:
space:
mode:
authorNicolas Lempereur <nle@odoo.com>2018-08-30 16:47:27 +0200
committerNicolas Lempereur <nle@odoo.com>2018-09-03 16:30:03 +0200
commit793988c7ed99b1b6e9a73efb94e438c7d0c7b34e (patch)
tree8573be2f8eb029c8d5eac65943f34d9996c1bf73 /addons/web/static/src/js/views/basic
parentb5471da2e0a5c8ef3b9fe35a933da25c97d8a6a2 (diff)
[FIX] web_editor: normal up/down in content in cell
In the editor in a table cell, when we press UP/DOWN keys: - we have default editor/browser behavior if there is content before (UP) or after (DOWN) the element we are currently on - else we go to the previous (UP) or next (DOWN) row if available - else we go to the next content if available - else we have the default editor/browser behavior But when checking if there is an element before/after the content, we did not take into account if there was an ancestor node inside the cell that had content after, so for example with this structure: ``` <table> <tr><td> <p>hello <b>world</b></p> <p>cruel</p> </td></tr> <tr><td> <p>bingo</p> </td></tr> </table> ``` if the current range was on 'world' text node, we would just check if there is content after this text node, not if there is content after its `<p/>` ancestor. Before the fix we would get on the next row, after we would have default editor/browser behavior: ie. if cruel is on another line, going to this line. opw-1870119 closes #26701
Diffstat (limited to 'addons/web/static/src/js/views/basic')
0 files changed, 0 insertions, 0 deletions