(This is split from bug 1828276 comment #8) > I think we should not allow a background page can open a picker and even switch itself to foreground. It's worth to check how other browser behave. However, in general, open a picker requires a user gesture, so blocking a background page from opening a picker should not cause web compatibility problem. Because in most of case "a-background-page == no-user-gesture", unless user interact with the page, switch it to background then tries to open a picker, and expect that work, but I think that is a very corner case. This is from a fullscreen sec bug, though we have a solution for that, bug 1821884, but not sure if this might cause other bugs, so file this bug for tracking and mark as a sec bug, too.
Bug 1837963 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(This is split from bug 1828276 comment #8) > I think we should not allow a background page can open a picker and even switch itself to foreground. It's worth to check how other browser behave. However, in general, open a picker requires a user gesture, so blocking a background page from opening a picker should not cause web compatibility problem. Because in most of case "a-background-page == no-user-gesture", unless user interact with the page, switch it to background then tries to open a picker, and expect that work, but I think that is a very corner case. This is from a fullscreen sec bug, though we have a solution for that, bug 1821884, but not sure if opening-pickers-from-background might cause other bugs, so file this bug for tracking and mark as a sec bug, too.