Need test for tab capture of inactive tabs to prevent future regressions |
||||||||||
Issue descriptionA recent change broke tab capture whenever the tab being captured was inactivated. It would cause tab capture to be suspended, effectively freezing any video being mirrored. We should add a browser test to chrome/browser/extensions/api/tab_capture/tab_capture_apitest.cc, something similar to the TabCaptureApiPixelTest.EndToEndWithoutRemoting test, but that also opens and switches to another tab and then makes sure tab capture continues to operate.
,
Jul 7 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11 2017
,
Sep 8 2017
,
Feb 1 2018
Issue 763541 has been merged into this issue.
,
Feb 1 2018
,
Feb 1 2018
,
Feb 7 2018
,
Feb 7 2018
,
Mar 20 2018
We really need to do this. We just had another regression where captured tabs would produce flickery output, with lots of blank black regions, if the tab is backgrounded. I'm raising priority and targeting M68 since we really need to catch these things before regressing CLs go into the tree.
,
Aug 3
miu@ are you planning to work on this? P1/P2 issues need an owner and milestone and must be fixed within 30days. If you're not planning to work on this, please drop to a P3.
,
Aug 6
=> miu to decide per c#11. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by sheriffbot@chromium.org
, Jul 7 2016