New issue
Advanced search Search tips

Issue 606039 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Always increase one dimension when calculating natural size.

Project Member Reported by xhw...@chromium.org, Apr 22 2016

Issue description

According to the spec related to video.videoWidth and video.videoHeight:

If an anamorphic format does not define how to apply the aspect ratio to the video data's dimensions to obtain the "correct" dimensions, then the user agent must apply the ratio by increasing one dimension and leaving the other unchanged.

Note that we should always "apply the ratio by INCREASING one dimension and leaving the other unchanged". Today in GetNaturalSize() we always keep the height unchanged and stretch/shrink the width, which seems wrong.

We should update our unittests and layout tests to cover this as well.
 

Comment 1 by xhw...@chromium.org, Apr 22 2016

dalecurtis / ddorwin: Do I interpret the spec correctly?

Comment 2 by xhw...@chromium.org, Apr 22 2016

Cc: phil...@opera.com
philipj: Please also help check whether I interpret the spec correctly. Thanks! :)

Comment 3 by phil...@opera.com, Apr 25 2016

That is the correct interpretation of the spec. It was changed in https://github.com/whatwg/html/commit/2e94aa64fcf9adbd2f70d8c2aecd192c8678e298 from previously always adjusting the width. There's no context given, but I know that I implemented what the spec now says in Presto and I think it makes sense, so I hope the change works out here.

Have you tested what Edge, Firefox and Safari do? In the unlikely even that all implementations already do the same thing, then I think we should revert the spec change instead.

Comment 4 by foolip@chromium.org, Nov 11 2016

Cc: foolip@chromium.org

Comment 5 by foolip@chromium.org, Nov 11 2016

Cc: -phil...@opera.com
Project Member

Comment 6 by sheriffbot@chromium.org, Nov 13 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by xhw...@chromium.org, Nov 13 2017

Labels: -Pri-3 Hotlist-Fixit Pri-2
Status: Available (was: Untriaged)
It seems this is something we should at least take a look. If we need to update, it should be a simple change.

Comment 8 by foolip@chromium.org, Nov 21 2017

Cc: -foolip@chromium.org
Cc: mlamouri@chromium.org
Project Member

Comment 10 by bugdroid1@chromium.org, Dec 13 2017

Owner: tmathmeyer@chromium.org
Status: Fixed (was: Available)
One last thing, did you check how other browsers handle this? Thanks!

Sign in to add a comment