- From: Dean Jackson via GitHub <sysbot+gh@w3.org>
- Date: Sat, 27 Jul 2019 01:21:07 +0000
- To: public-css-archive@w3.org
This isn't going to be useful feedback, but these suggestions probably sound terrifying to implementers. One of the reasons an OS window system can do this is because it doesn't have anything like the complexity of CSS layout. It just draws bitmaps in a particular order (and they often still fall short in some of the examples above). Take the <select> or pop-up menu. In a native control, that is a modal window that appears over everything. If you swap windows (apps), it goes away. You can't scroll the originating window while the overlay is up. (You might be able to programatically scroll the original window, but I wouldn't be surprised if the overlay doesn't move). All this is special behaviour for a particular UI interaction. If you stick to native controls in CSS, then maybe it will work. The native <select> does what was requested, for example. However, if you're asking for the ability to have anything escape its container, and possibly its window, then things will get really difficult. For one thing, do they become modal? Under what circumstances do they fall out of this mode? etc. -- GitHub Notification of comment by grorg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4092#issuecomment-515640291 using your GitHub account
Received on Saturday, 27 July 2019 01:21:08 UTC