I noticed in my integration that since 15.2 I get unexpected calls on the WSEditorChangeListener.editorActivated method.

In my plugin I create an WSEditorChangeListener for the map manager and the editor view on initialization. So each panel/view has its own listener.

Since 15.2 I noticed that the editorActivated was called on both listeners. Didn’t really matter if a document was opened in the map manager or editor view. In my case I was only expecting it to be called within the listener of the editor view.

For example when you open a document like “paint.dita” in the editor view, I can see the editorActivated being called for both the map manager and the editor. Both have the url of that file as an editorLocation parameter.

I can get round this issue by getting the WSEditor instance and check if it is null.

Kind regards