Xidorn Quan

That is #24.

That's a... good question. In Gecko's implementation, you cannot, but the spec seems to indicate that you should be able to... I guess I can make Gecko behave that way...

I don't really think the data from Chromium makes a lot of sense, because authors who use webkit-prefixed API likely also try other prefixed API at the same time, and...

It doesn't seem that Gecko needs it so far? Does it make sense to try removing it from Chromium as the next step? It would be great if we don't...

These manual tests are checking against hierarchy restrictions: * fullscreen/api/element-ready-check-fullscreen-element-sibling-manual.html * fullscreen/api/element-request-fullscreen-non-top-manual.html * fullscreen/api/element-request-fullscreen-two-elements-manual.html

(For my own note: there was [a Gecko bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1195213) we can reuse if we end up not reverting the change.)

> Think of a series of divs that are all siblings and you click 'next'. Which would change the fullscreen element to the next element. That is not a usecase...

Also, if we are re-introducing the hierarchy restriction, we may need to revisit [bug 27865](https://www.w3.org/Bugs/Public/show_bug.cgi?id=27865) and see how modal dialog would need to interact with fullscreen...

> Also, change the description so that it just says "fixes #1247". The prefix means it won't autoclose the issue when this is merged. I don't think that's true: 

> (And I blame Github not showing a visual indicator on that. I remember it showing a dashed underline in the past.) It does show a dashed underline for me,...