Issue 559394 is actively ignored
Reported by
shir...@gmail.com,
Oct 8 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: Steps described here: https://bugs.chromium.org/p/chromium/issues/detail?id=559394 What is the expected behavior? What went wrong? Description here: https://bugs.chromium.org/p/chromium/issues/detail?id=559394 Did this work before? No Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.12.6 Flash Version: Please keep in mind that this is a very very old issue. It has been ACK-ed by you guys, I have also provided the fix for it. yet is still unresolved. People came and went away on this issue. I have opened this new issue because I believe somehow the old one felt through some cracks. This issue is hurting a lot of projects using WebRTC and wanting to interoperate with chrome. Keep in mind that Chrome/Firefox, Chrome/(soon)Safari and Chrome/(soon)Edge is broken because of this
,
Oct 8 2017
Updated link to the proof of fault: https://www.dropbox.com/s/z28q2zlg58mo3sw/chrome_bug_report.mov?dl=0
,
Oct 9 2017
,
Oct 9 2017
cc'ing deadbeef@ and hbos@ from Issue 559394 for more inputs.
,
Oct 9 2017
It's not being actively ignored (I think that's a bit of an oxymoron). I've been planning to review your patch, I've just been busy lately. I should be getting to it sometime this week.
,
Oct 9 2017
Okay, I have to admit, poor wording. Looking forward to any progress. Thanks |
||||
►
Sign in to add a comment |
||||
Comment 1 by shir...@gmail.com
, Oct 8 201724.7 KB
24.7 KB Download