When using any of the jump commands in ChromeVox, e.g. next/previous heading, next/previous table and next/previous link, they don't work if such jump targets are found within a content editable.
We should allow a user to use at least some of these jump commands when in a content editable. This is very helpful if the user is browsing a document in Google Docs and even though Docs already has a set of jump commands of its own, it would be better if the same commands provided by the screen reader were available everywhere.
I don't think that these jump commands should work if the focus is not on the content editable, to avoid moving the caret unintentionally while casually browsing through the page. For example, if the user is browsing through all the links in the page but the focus is not on the content editable, the jump command for links should not go through any links in the content editable. Conversely, if the focus is in the content editable, jump commands should restrict themselves to the content editable.