https://bugs.documentfoundation.org/show_bug.cgi?id=146443
--- Comment #11 from Mike Kaganski <mikekagan...@hotmail.com> --- (In reply to Aron Budea from comment #10) > The fact that this affects external programs calling into LO via UNO is an > unfortunate side-effect. I wonder if/how other similar changes have been > handled in the past, I'm sure there were several convenience changes before > that could've had a similar kind of impact, eg. the change to default > anchoring. Note that the external program that we are discussing uses *cursor* API, i.e., the API which is intended to do the same as what user does with their cursor. Every API has some guarantee; for cursor, every programmer should realize that its guarantee is *to match UI behavior*. And that doesn't mean that that API disables each and every possible improvement in UI (just because such improvements can naturally change UI behavior) - it means that the API will follow the respective changes. So I believe that there's nothing "broken" in API, but someone could use it without realizing what it guarantees. Instead, one could use paragraph enumeration to get the specific parts in the document, and then be completely independent from UI. -- You are receiving this mail because: You are the assignee for the bug.
