Opened 11 years ago

Closed 11 years ago

#2809 closed bug (fixed)

Screen saver window can be in front of the password window

Reported by: axeld Owned by: axeld
Priority: high Milestone: R1
Component: User Interface Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Since the password window and the screen saver windows both have the kWindowScreenFeel at the moment, you can move the screen saver window in front of the password window just by clicking on it.

Currently, modal windows (even modal all windows) always appear behind a kWindowScreenFeel (like in BeOS). However, logically, an modal app or a modal all window should be able to be in front of a kWindowScreenFeel window, even though this would be different from BeOS.

I would suggest to allow modal windows to appear above others always, no matter what feel. Additionally, I would add a modal feel that is even above B_MODAL_ALL_WINDOW_FEEL, ie. a kPasswordModalAllWindowFeel that would make it possible to make the Team Monitor inaccessible.

Opinions welcome.

BTW the only method to regain control if the above happens is to use F12 to drop into the kernel debugger, and then let the screen_blanker app crash using the "drop" command.

Change History (3)

comment:1 Changed 11 years ago by anevilyak

Would it perhaps be prudent to maybe make this mechanism a bit more integrated into one of the servers directly so as to prevent misuse? If we introduce such a flag, what's to stop an app from abusing it? Perhaps it should be restricted such that only certain users (say, root or whatever user the screensaver server winds up running as) could create windows with that feel?

comment:2 Changed 11 years ago by the ringmaster

I just tried hrev27946 and this is no longer a problem. The deskbar doesn't show and the password windows says in the foreground. nice work

comment:3 Changed 11 years ago by axeld

Resolution: fixed
Status: newclosed

Fixed in hrev28281.

Note: See TracTickets for help on using tickets.