video not always scaled to fit window

[jpiesing]

I've seen a couple of times when the video for encrypted content playback is not scaled to fit the window.

I does the same on a desktop if you make the browser window smaller than the video.

[louaybassbouss]

@FritzHeiden can you check

[FritzHeiden]

I am unable to reproduce your issue:

What version do you use (commit id)? Or you did you deploy the test runner?

[jpiesing]

I was seeing this twice in 3 times when I ran the test.
I just just whatever was the head of the trunk (i.e. ./build.sh --reload-tests --reload-runner).

[FritzHeiden]

After taking another look at the screenshots, it seems like there is no css applied to the page. Maybe this is an issue with loading the css file. I'm still not sure what may cause this.

[jpiesing]

After taking another look at the screenshots, it seems like there is no css applied to the page. Maybe this is an issue with loading the css file. I'm still not sure what may cause this.

Would there be any error messages if this had happened?

[FritzHeiden]

There should be an error stating that loading the css file failed. I did not explicitly implement it.

[jpiesing]

I've just tried the encrypted content playback again and I get this issue every time. There's nothing in the messages in the report afterwards. Here are all references to CSS in the docker log.
docker-log-css-references.txt
There's no 403s or 40 anythings. I'll upload a screenshot from the phone while this is happening.

[jpiesing]

Here's a screen capture from the phone with encrypted content playback running. You can see that the browser graphics are not overlaying the video any more.

[louaybassbouss]

@jpiesing if you open the same test in Chrome Desktop (via same IP and not localhost) do you see the same issue? if yes can you open the Developer console -> Network Tab and check if there are errors while downloading some files (especially CSS). If the issue only happens on the Android Tablet, is there any chance to get a screenshot of the developer console on the tablet via remote debugging (https://developer.chrome.com/docs/devtools/remote-debugging/)?

[jpiesing]

@jpiesing if you open the same test in Chrome Desktop (via same IP and not localhost) do you see the same issue? if yes can you open the Developer console -> Network Tab and check if there are errors while downloading some files (especially CSS).

Yes - it happens with Chromium on Linux - at least once. The second time, it worked. Once it works the first time, it continues to work. I'm investigating if clearing the cache will make it revert to breaking.

[jpiesing]

Clearing the cache seems to make it repeatable.

[jpiesing]

This one is off the phone.

[jpiesing]

Umm. I wonder if it's this ...

https://www.titanwolf.org/Network/q/51138767-7580-4885-9ec0-a8ceb03703c4/y

which refers to this old Chrome bug - which shows no sign of getting fixed.

https://bugs.chromium.org/p/chromium/issues/detail?id=488043

"The issue is resolved when I use a valid certificate instead of a self-signed one for my web application. Further details can be found by visiting the above URL."

[FritzHeiden]

Clearing the cache seems to make it repeatable.

I was able to reproduce the behavior for some time. I added a dummy.css before the style.css, hoping the error occurs with the dummy, rather than the actual style. I was unable to test it as I was unable to reproduce the bug after I implemented it. @jpiesing Could try to rerun tests with these changes and see if this may fix the issue?

[jpiesing]

I was able to reproduce the behavior for some time. I added a dummy.css before the style.css, hoping the error occurs with the dummy, rather than the actual style. I was unable to test it as I was unable to reproduce the bug after I implemented it. @jpiesing Could try to rerun tests with these changes and see if this may fix the issue?

@FritzHeiden Please check that you actually checked this in. When I re-run the tests, the problem is still there.

[jpiesing]

[gitwjr]

Document the issue in Readme as a list of known bugs. Request people doing testing to report if they still see them happening.
@FritzHeiden to document.

[FritzHeiden]

I added a list of known bugs, including this one here