All calls to explorer package should be only from
AWT-queue. explorer and explorer/view package
contains visualization of data thus calls and
events must be from AWT. The change events in
ExplorerManager are replanned to AWT-queue now but
it can lead to a unexpected behavior.
See also issue 27462 - Some ExplorerViews do not conform to Swing
Will probably be fixed in issue #35833's branch.
Assigned to new owner.
Reassigning to new module owner Tomas Holy.
Probably no real benefits over current state.