https://issues.apache.org/ooo/show_bug.cgi?id=123460
--- Comment #7 from Brant Watson <[email protected]> --- @brinzing - I think it might actually be the other way around. It seems to me that the "document is closing" and "document closed" events are both important (the distinction is there for a reason anyway), and anytime a document is closed one would expect to see both events fired. It probably makes more sense to figure out why XClosable doesn't trigger both events as opposed to checking the menu code to figure out why its firing both. There are probably two seperate codepaths for closing a document happening, otherwise there wouldn't be a behaviour descrepancy. Whatever the reason though, I think the correct fix would be to make sure that XClosable properly fires the "document is closing" event. -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
