Issue metadata
Sign in to add a comment
|
Regression: Timestamp not seen in peerconnection/audio demo page |
||||||||||||||||||||||
Issue descriptionApplication Version (from "Chrome Settings > About Chrome"): M55 55.0.2880.0 Android Build Number (from "Android Settings > About Phone/Tablet"): Android N build NPD35C Device: Nexus 5X Steps to reproduce: 1. Open https://webrtc.github.io/samples/src/content/peerconnection/audio/ in Clank M55 2. With any codec listed, click 'Call' 3. Observe the timestamp against the 'Remote audio' bar Observed behavior: The timestamp is not seen Expected behavior: The timestamp should be seen, incrementing Frequency: 5/5 times <number of times you were able to reproduce> Additional comments: 1. This issue is not seen in M54 Beta in the same device 2. Logs and screenshot below
,
Oct 5 2016
jansson: can you have a look to see if it's a problem in the demo page or if it's a bug in Chrome?
,
Oct 5 2016
It seems like the dimensions in the audio tag has changed between M55 and M54. If I change the width to 354px the timer disappears on M55 whilst it disappears at 294px on M54. This was on Linux, I assume this affects all platforms. Since the demo page has not changed I think we should raise this with the CSS or audio tag people to see if this is a intentional change.
,
Oct 5 2016
This issue is not observed in Chrome OS with M55 55.0.2878.0 / 8861.0.0 dev
,
Oct 5 2016
So far I see this issue only in Android Clank M55, but not in M55 Canary/Dev in Win, Mac, Linux
,
Oct 5 2016
Marking it as needs bisect to get the CL and if it is an Interop change we can take it from there and ask the author of the CL. Defaulting to set TL as owner in the meanwhile.
,
Oct 6 2016
#5 I can see it on desktop if I reduce the window size as I mentioned in #3. Have you tried that? I did notice the absolute pixel values were different if I used dev tools to change the window size rather than just changing the window size.
,
Oct 6 2016
jansson@ - Ah yes, I see it now (timer disappears) when I resize the window
,
Oct 10 2016
,
Oct 10 2016
We can't bisect this if it's restrict-view-google, so since it repros on desktop, reposting screenshots and removing internal link. Note that I had to set a smaller width of 354px on the body element using dev tools to reproduce this. We also can't fully triage this until the bisect comes in, so returning the status to Untriaged.
,
Oct 12 2016
I think the latest redesign of the media element controls is the cause. Time display and duration disappear first when they don't fit. This CL changed that AFAIK: https://codereview.chromium.org/2301823002. +Rachel on her thoughts - perhaps when we're streaming/recording audio the time is more important than other controls? Not sure if it's easy to change the priorities dynamically yet.
,
Jun 6 2017
As comment #11 mentions, this is working as intended. We are aware that the new design is a bit agressive for small controls. You can increase the width and you should see the timestamp. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted