- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 Nov 2012 00:13:31 +0000
- To: public-texttracks@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19744
Silvia Pfeiffer <silviapfeiffer1@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #7 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> ---
No, I actually can't leave this alone. :-)
As currently specified, the edge margin is only applied to the left and right
edges of the video (for horizontal cues). So, when we have overscan and are
positioning in line -1, the left and right edges of the cue get the margin, but
the cue still sits at the bottom boundary of the video viewport. (This is
independent of whether the cue has a position value or not.)
Even given your condition that the edge margin is only applied to
non-explicitly positioned cues - we still need to also apply it in y-position
direction, not just in x-position dimension.
That all makes me wonder whether it wouldn't be easier to drop the whole idea
of edge margin and instead tell players that need to avoid overscan to make use
of the technique in bug 17273.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 1 November 2012 00:13:33 UTC