[Bug 23280] Make positioning values % instead of 'vh' and 'vw'

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23280

Philip Jägenstedt <philipj@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #7 from Philip Jägenstedt <philipj@opera.com> ---
(In reply to Rick Eyre from comment #6)
> (In reply to Philip Jägenstedt from comment #3)
> > In both implementations I have worked on (Presto and Blink) it's the case
> > that the vh/vw isn't actually used internally, because as Rick says it's
> > extra work to make them relative to the video in this special case. Instead,
> > in Presto we just did the calculation using the video size internally, and
> > in Blink percentages are used instead.
> > 
> > So, I'm quite sympathetic to having the spec use percentages instead.
> > However, I think the vh/vw units have a purpose for styling the text using
> > CSS. Without them, is there actually any unit one could use to make the text
> > grow and shrink with the video? This seems important to have, and the work
> > required to support that is the same as is required to allow the
> > implementation to use them internally as well...
> > 
> > Thoughts?
> 
> Yes, I see your point. Internally Firefox uses percentages that are relative
> to the video view port. Which technically is 'vw and vh with the initial
> containing block redefined to the video viewport'. But we don't go through
> the trouble of actually redefining the viewport and using vh and vw units.
> 
> However, I can see how from the authors point of view it might make more
> sense to use vh or vw when setting WebVTT styles since their concern is only
> with the styles of the captions at that point.

How have you worked around the fact that the default font is '5vh sans-serif'?

Regardless, I think that viewport-relative units in author-provided CSS is too
important to give up on, so we'll just have to try to implement this instead.
If that doesn't happen within a few years or if multiple vendors say it's just
too hard (doubtful) then we'll have to revisit this issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 28 January 2014 17:02:54 UTC