Bug #12883
closed[Composer] Chrome silently suppresses window.open() when using "run" button
100%
Updated by Peter Amstutz about 7 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz about 7 years ago
- Status changed from In Progress to New
Updated by Peter Amstutz about 7 years ago
- Assigned To changed from Peter Amstutz to Lucas Di Pentima
Updated by Peter Amstutz about 7 years ago
Chrome's policy is to only open popups if the call to window.open() is directly on the call stack of an input event. The problem is, this doesn't play nicely with the deferred execution strategy used everywhere in Composer. One option is to create a modal dialog with a link "click here to go to workbench" link.
Updated by Lucas Di Pentima about 7 years ago
- Target version changed from 2018-01-17 Sprint to 2018-01-31 Sprint
Updated by Tom Clegg about 7 years ago
Rather than doing an ajax request (or whatever the async procedure is) that opens a Workbench window in its success callback, would it work to immediately open a window that starts the async procedure and then redirects to Workbench on success?
Updated by Peter Amstutz about 7 years ago
- Assigned To changed from Lucas Di Pentima to Peter Amstutz
Updated by Peter Amstutz about 7 years ago
- Target version changed from 2018-01-31 Sprint to 2018-02-14 Sprint
Updated by Peter Amstutz almost 7 years ago
The workaround here is to provide clickable link in the "execution" panel which opens a new window, so if window.open() is suppressed the user can still easily get to the container request.
Updated by Peter Amstutz almost 7 years ago
Change in note-11 was made in commit:cf8b76c9a983de933fc6ffb934d9732c2a2bf0e7
Updated by Peter Amstutz almost 7 years ago
- Status changed from New to Resolved