chrome.tabs.captureVisibleTab not working on ARM Processors
Reported by
aa...@rumbold.me.uk,
May 19 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS armv7l 8172.28.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.42 Safari/537.36 Platform: 8172.28.0 (Official Build) beta-channel daisy Steps to reproduce the problem: I have created a simple test scenario to reproduce the problem with chrome.tabs.captureVisibleTab You can see the captureVisibleTab method working correctly by installing on an Intel based device. The screen capture does not work with an ARM based device. I believe this may have the same underlying cause as Issue 612069 but it is also affecting Chrome 51 1. Download the test extension and test applications from gitlab: https://gitlab.com/arumbold/chrome-tab-capture/repository/archive.zip?ref=master https://gitlab.com/arumbold/chrome-tab-display/repository/archive.zip?ref=master 2. Unzip and install the extensions 3. In the options page of chrome-tab-capture, specify the Extension ID of chrome-tab-display (This will send the tab screenshots to there) go to any page in your chrome browser. You should see a screenshot of the active tab. What is the expected behavior? Screenshots obtained from chrome would contain a picture of the tab What went wrong? Screenshots appear garbled. Did this work before? Yes It works in the current released Chrome 49.0.2623.112 (veyron_minnie) stable channel Chrome version: 51.0.2704.42 Channel: beta OS Version: 8172.28.0 Flash Version: Shockwave Flash 22.0 r0 Don't leave the extensions running for a long time, they gobble memory.
,
May 24 2016
Comment 6 in Issue 612069 by djkurtz@chromium.org Status: Fixed Fixed on oak as of 8341.0.0 Fixed on daisy/peach/veyron as of 8350.0.0. OK to close.
,
May 24 2016
Can I confirm - This is fixed in platform versions > 8350 / 8341 Will this fix propagate to Chrome 51 (Beta / Stable), or will Chrome 51 still be broken on ARM when it goes live?
,
May 27 2016
,
May 27 2016
Remarking as the Extensions API component since that seems best suited. As far as I can tell this issue is unrelated to the DevTools functionality.
,
Jul 19 2016
Approx 2.5M students affected in v51, requesting propagation to 51 to avoid pushing all organizations to dev channel
,
Jul 20 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||
►
Sign in to add a comment |
||||
Comment 1 by aa...@rumbold.me.uk
, May 20 2016