-
- Downloads
[FIX] board: stop the propagation of custom events
Recently, rev. 5b3cb812 added a new custom event ('update_filters') handler to the ActionManager, and rev. 69c9500e added an option ('keepSearchView') to doAction (which can be called by triggering up event 'do_action'). Both events ('update_filters' and 'do_action') can be triggered by controllers, and when those controllers were in the dashboard, a crash occured when they triggered those events. In particular, they are triggered by the new 'web_dashboard' view, respectively when clicking on an aggregate and when clicking on the subview button to open it full screen. The crashes occurred because the events weren't intercepted by the dashboard, so they bubbled up to the ActionManager which couldn't handle the requests properly as it wasn't aware of those sub controllers. As there is no search view in the dashboard, the 'update_filters' event simply needs to be stopped (we can't handle such a request in the dashboard), and for the 'do_action' event, the 'keepSearchView' option must be forced to false as there is no search view to keep (we thus force the ActionManager to create a new one).
Please register or sign in to comment