[whatwg] api for fullscreen()
bzbarsky at MIT.EDU
Fri Jan 29 06:36:32 PST 2010
On 1/28/10 10:41 PM, Kit Grose wrote:
> True, but surely saying "any element" opens the door to full-screening inline text elements (e.g<span> elements).
I don't see why this is a problem, offhand.
> I suppose the native style being "position: fixed" would put those elements in a block formatting context anyway
More precisely would make them block-level in CSS terms. A block
formatting context is something different.
> but what implications might that have for things like table cells/table rows being made full-screen?
For table cells, none whatsoever.
For table rows, that's a good question. If one just makes them
position:fixed, that would basically mean you create an anonymous table
inside the row (in particular, you redo column balancing on the row's
cells while ignoring all the other rows of the table). Is that the
desired behavior? If not, what is? There may be no good solutions here.
The other interesting thing with table rows is what should happen with
cells spanning into the row or out of it. With the position:fixed
approach the former would not appear and the latter would just be
visible in their entirety. Again, it's not clear to me whether there's
a "good" behavior here.
More information about the whatwg