Support for positioning a pop-up window on the secondary screen

%3CLINGO-SUB%20id%3D%22lingo-sub-1525847%22%20slang%3D%22en-US%22%3ESupport%20for%20positioning%20a%20pop-up%20window%20on%20the%20secondary%20screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1525847%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20references%20%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D137681%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D137681%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Internet%20Explorer%2C%20Microsoft%20Edge%20v44%2C%20and%20Mozilla%20Firefox%2C%20it%20is%20possible%20to%20open%20a%20popup%20window%20on%20the%20secondary%20screen%20%2F%20and%20or%20on%20the%20left%20screen.%20This%20scenario%20is%20required%20for%20all%20types%20of%20enterprise%20applications%20that%20display%20large%20amounts%20of%20data%20to%20provide%20a%20consitent%20and%20efficient%20user%20experience.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Chromium%2C%20this%20feature%20was%20removed%20and%20there%20is%20now%20an%20ongoing%20discussion%20since%202012%20on%20this%20subject.%20Could%20someone%20please%20take%20a%20look%20at%20this%20because%20right%20now%2C%20it%20is%20a%20major%20gap%20of%20Microsoft%20Edge%20v79%2B%20comapered%20to%20other%20major%20browsers%20as%20well%20as%20a%20regression%20with%20the%20previous%20version%20of%20Microsoft%20Edge%20before%20the%20platform%20has%20switched%20to%20Chromium.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%20Michael%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1552202%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20for%20positioning%20a%20pop-up%20window%20on%20the%20secondary%20screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1552202%22%20slang%3D%22en-US%22%3E%3CP%3EMichael%20Wasserman%20provides%20a%20comprehensive%20answer%20here%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fwebscreens%2Fwindow-placement%2Fissues%2F15%23issuecomment-665415786%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fwebscreens%2Fwindow-placement%2Fissues%2F15%23issuecomment-665415786%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CP%3EThe%20current%20proposal%20would%20enable%20saving%20and%20restoring%20cross-screen%20window%20placements%20without%20new%20APIs%2C%20but%20perhaps%20gated%20on%20a%20new%20permission.%20See%20the%20saveOpenWindows()%20and%20restoreSavedWindows()%20example%20in%20this%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fwebscreens%2Fwindow-placement%2Fblob%2Fmaster%2FEXPLAINER.md%23support-requests-to-place-web-app-windows-on-a-specific-screen%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Esection%3C%2FA%3E%20of%20the%20updated%20explainer.%20Chrome's%20highly%20speculative%20and%20aspirational%20%3CA%20href%3D%22https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1de0ZYDOcafNXXwMcg4EZhT0346QM-QFvZfoD8ZffHeA%2Fedit%23gid%3D272423396%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Etime%20frame%3C%2FA%3E%20is%20origin%20trial%20in%20M-86%20and%20broader%20availability%20in%20M-89.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

This references https://bugs.chromium.org/p/chromium/issues/detail?id=137681

 

In Internet Explorer, Microsoft Edge v44, and Mozilla Firefox, it is possible to open a popup window on the secondary screen / and or on the left screen. This scenario is required for all types of enterprise applications that display large amounts of data to provide a consitent and efficient user experience.

 

In Chromium, this feature was removed and there is now an ongoing discussion since 2012 on this subject. Could someone please take a look at this because right now, it is a major gap of Microsoft Edge v79+ comapered to other major browsers as well as a regression with the previous version of Microsoft Edge before the platform has switched to Chromium.

 

Thanks, Michael

1 Reply
Highlighted

Michael Wasserman provides a comprehensive answer here:

https://github.com/webscreens/window-placement/issues/15#issuecomment-665415786

 


The current proposal would enable saving and restoring cross-screen window placements without new APIs, but perhaps gated on a new permission. See the saveOpenWindows() and restoreSavedWindows() example in this section of the updated explainer. Chrome's highly speculative and aspirational time frame is origin trial in M-86 and broader availability in M-89.