Issue metadata
Sign in to add a comment
|
Simultaneous connections to Chrome Debugging Protocol - crash
Reported by
mzygmu...@gmail.com,
Dec 13 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: https://bugs.chromium.org/p/chromium/issues/detail?id=129539#c3 What is the expected behavior? What went wrong? We lost all hope. Did this work before? No Chrome version: 55.0.2883.87 Channel: stable OS Version: OS X 10.12.1 Flash Version: Shockwave Flash 24.0 r0
,
Dec 13 2016
fwiw, comments are restricted on the original bug; it would be welcome to get an update from the Chrome team as the planned update (per paulirish) is 3 years overdue, and the last communication is a 1 year old request for triage (from laforge).
,
Dec 14 2016
We're waiting for fix since 2012, so we'll wait a few more years ...
,
Dec 15 2016
You'll be surprised, but we are still working on this feature :) I hope it comes to a resolution sooner than within 3 more years.
,
Dec 15 2016
Nice to hear that the issue isn't ignored. I take your word for it. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by chenwilliam@chromium.org
, Dec 13 2016Status: Duplicate (was: Unconfirmed)