Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)

@tabatkins commented on this pull request.



> + <li><p><a>Request removal from the top layer</a> given <var>element</var>.
+
+ <li><a>Add to the top layer</a> given <var>element</var>.

I'm not sure what you mean by "allow for slightly novel behavior in new APIs". All APIs would cycle thru the algorithms in this same way, unless they wanted to get into the guts and directly manipulate the top layer list (which they shouldn't).

The only two behaviors that specs should end up landing on for "put something in the top layer when it's already there" are this (cycle it to the end of the list) and "fail", probably throwing an error when they do so.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/pull/223#discussion_r1201154002
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fullscreen/pull/223/review/1437661095@github.com>