Community
Participate
Working Groups
On bug 184475, comment 2 Michael said: "(...) we need API on ContentMergeViewer that we can call to indicate that a viewer change is about to take place. I worked around this in 3.3 by adapting TextMergeViewer to an internal class in order to deactivate the handlers (This doesn't work for ContentMergeViewer since it doesn't implement IAdaptable). However, I think the best API to add in 3.4 is just a method on ContentMergeViewer that gets called before the viewer switch happens."
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.