W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

[Bug 27863] New: Not need to specify moving element in top layer and fullscreen stack

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Jan 2015 06:05:50 +0000
To: public-webapps@w3.org
Message-ID: <bug-27863-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27863

            Bug ID: 27863
           Summary: Not need to specify moving element in top layer and
                    fullscreen stack
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Fullscreen
          Assignee: annevk@annevk.nl
          Reporter: quanxunzhen@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

https://fullscreen.spec.whatwg.org/#concept-fullscreen-add

[[
To add an element on a document's fullscreen element stack, add, or move if
already present, it on top of document's browsing context's top layer, and then
add, or move if already present, it on top of document's fullscreen element
stack.
]]

Since the spec includes the following items in the "fullscreen element ready
check" algorithm:

[[
element's node document's fullscreen element stack is either empty or its top
element is an inclusive ancestor of element. 
]]

I don't think it is possible that an element already in the stack could be
added to the stack again.

Hence I suggest to remove the "or move if already present".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 20 January 2015 06:05:51 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC