|
I am sorry but we can get you close but not that close. We use the concept of a web path inside the Preview DOM tree where you click to determine the approximate location within the file in CodeView. The problem is that the DOM tree needs to be normalized so that sequential text nodes are properly merged into one but this normalization action resets the Preview cursor losing its location. It also requires the text being edited in CodeView to be fully well formed and properly constructed so the Preview WebPath can match a CodeView tag path. So given how locations are shared between a text position in CodeView to a Web path to a normalized text node and visa versa, the syncing is imprecise but should be very close unless javascripts have changed the DOM.
So this is not going to happen.
Sorry.
|