Closed Bug 1519893 Opened 5 years ago Closed 5 years ago

Add an alwaysontop window feature for Windows

Categories

(Core :: Widget: Win32, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

Details

(Keywords: dev-doc-complete)

Attachments

(2 files)

This will be a chrome-only extension to the window.open feature string list. I imagine the string will be "alwaysontop", and the resulting window should have a sufficiently high z-index to always be visible on top of other windows.

Assignee: nobody → mconley

I'm going to try to get some tests put together for this too in a separate patch.

These tests make sure that passing alwaysOnTop as a window feature
results in a window with WS_EX_TOPMOST, and also ensures that web
content cannot request alwaysOnTop windows.

Depends on D16486
Blocks: 1520329
Attachment #9036390 - Attachment description: Bug 1519893 - Add alwaysontop chrome-only window feature for Windows. r?aklotz → Bug 1519893 - Add alwaysOnTop chrome-only window feature for Windows. r?aklotz
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2d7f5838e68f
Add alwaysOnTop chrome-only window feature for Windows. r=aklotz
https://hg.mozilla.org/integration/autoland/rev/45b6acf51517
Test the alwaysOnTop feature for Windows. r=aklotz

So IIUC, the difference between the new "alwaysontop" feature and the existing similarly named "alwaysRaised" one is that the latter stays on top of non-browser windows? Is that right and are their other differences. I think this should be documented on MDN since the difference isn't documented in code comments.

https://developer.mozilla.org/en-US/docs/Web/API/Window/open#Features_requiring_privileges

Keywords: dev-doc-needed
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66

I've added an entry about this new feature on https://developer.mozilla.org/en-US/docs/Web/API/Window/open#Window_features

I was not intending to add a note to the 66 rel notes about this as it is a Chrome only feature.

I think we can call the docs done for this one, unless you'd like me to update the wording in some way.

You need to log in before you can comment on or make changes to this bug.