Hi I do not really understand these recent changes in this bugs status. Why was the bug forwarded to a chromium issue that hasn't seen any activity since september last year? The "55.0.2883.75-3" release fixed the problem by disabling the built-in media-router, but as described, the router was somehow re-eanbled in "56.0.2924.76-3". The chromium issue only describes how the router now only works in the official Chrome build, so how is this relevant to the current situation?
