Re: [whatwg] [css-display] CSS Display Review

2016-09-19 Thread Mats Palmgren
On 09/20/2016 02:54 AM, Boris Zbarsky wrote: On 9/20/16 1:46 AM, Mats Palmgren wrote: Assuming that the above are the final DOM trees, then they should create exactly the same CSS boxes as if the element is replaced by its (DOM) children. That contradicts what fantasai claimed the spec says.

Re: [whatwg] [css-display] CSS Display Review

2016-09-19 Thread Boris Zbarsky
On 9/20/16 1:46 AM, Mats Palmgren wrote: Assuming that the above are the final DOM trees, then they should create exactly the same CSS boxes as if the element is replaced by its (DOM) children. That contradicts what fantasai claimed the spec says. Which brings me back to my claim that the

Re: [whatwg] [css-display] CSS Display Review

2016-09-19 Thread Mats Palmgren
On 09/20/2016 12:53 AM, fantasai wrote: legend and what about: details Text. Assuming that the above are the final DOM trees, then they should create exactly the same CSS boxes as if the element is replaced by its (DOM) children. (The only

[whatwg] [css-display] CSS Display Review

2016-09-19 Thread fantasai
(I'm guessing you don't mind if I forward your comments to the ML. Feel free to scold me for presumptuousness if not. ;) CCing WHATWG for comments on HTML interaction (or any other comments they may have); follow-ups to www-st...@w3.org. On 08/29/2016 06:52 PM, Boris Zbarsky wrote: On 8/2/16

Re: [whatwg] possible new parameters to video.play() ?

2016-09-19 Thread Simon Pieters
On Sun, 18 Sep 2016 18:45:51 +0200, Melvin Carvalho wrote: The pauseOnExit attribute on VTTCue can be used for this purpose. See https://html.spec.whatwg.org/multipage/embedded-content.html #text-track-api:the-audio-element for an example. Thank you for both