Bug 230825

Summary:

It looks tabs.captureVisibleTab returns buggy image

Product:

WebKit

Reporter:

pasta0915

Component:

New Bugs

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED MOVED

Severity:

Normal

CC:

bweinstein, katherine_cheney, thorton, timothy, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

Other

Hardware:

iPhone / iPad

OS:

Unspecified

Attachments:

Description	Flags
(outdated)	none
Image taken by tabs.captureVisibleTab	none
Screenshot taken by iPad native	none
Image taken by tabs.captureVisibleTab	none
marked up area to expect	none

pasta0915

Reported 2021-09-27 03:57:21 PDT

Created attachment 439340 [details] (outdated) My environment is mobile Safari 15 on iPadOS. When display Calling `chrome.tabs.captureVisibleTab` and then get

Attachments
(outdated) (151.88 KB, image/jpeg) 2021-09-27 03:57 PDT, pasta0915	no flags	Details
Image taken by tabs.captureVisibleTab (1.00 MB, image/png) 2021-09-27 03:59 PDT, pasta0915	no flags	Details
Screenshot taken by iPad native (5.01 MB, image/png) 2021-09-27 04:14 PDT, pasta0915	no flags	Details
Image taken by tabs.captureVisibleTab (1.12 MB, image/png) 2021-09-27 04:15 PDT, pasta0915	no flags	Details
marked up area to expect (818.81 KB, image/png) 2021-10-06 20:45 PDT, pasta0915	no flags	Details
Show Obsolete (2) View All Add attachment proposed patch, testcase, etc.

pasta0915

Comment 1 2021-09-27 03:59:12 PDT

Created attachment 439341 [details] Image taken by tabs.captureVisibleTab

pasta0915

Comment 2 2021-09-27 04:12:17 PDT

I'm sorry I posted #1 not completely post by mistake. I rewrite here: My environment is mobile Safari 15 on iPadOS. When displaying like "Screenshot taken by iPad native", my extension calls `chrome.tabs.captureVisibleTab` and then it gets like "Image taken by tabs.captureVisibleTab". On Safari 15 on macOS, `chrome.tabs.captureVisibleTab` gives an image as same as the rendering user looks. It looks good because Chrome and Firefox have also the same behavior. Why Safari on iOS gives us mysterious results. Do you have any plan to fix? Thanks

pasta0915

Comment 3 2021-09-27 04:14:56 PDT

Created attachment 439342 [details] Screenshot taken by iPad native

pasta0915

Comment 4 2021-09-27 04:15:24 PDT

Created attachment 439343 [details] Image taken by tabs.captureVisibleTab

Radar WebKit Bug Importer

Comment 5 2021-09-28 10:56:58 PDT

<rdar://problem/83630466>

Brian Weinstein

Comment 6 2021-10-06 15:43:11 PDT

(In reply to pasta0915 from comment #2) > I'm sorry I posted #1 not completely post by mistake. > > I rewrite here: > > My environment is mobile Safari 15 on iPadOS. > > When displaying like "Screenshot taken by iPad native", my extension calls > `chrome.tabs.captureVisibleTab` and then it gets like "Image taken by > tabs.captureVisibleTab". > > On Safari 15 on macOS, `chrome.tabs.captureVisibleTab` gives an image as > same as the rendering user looks. It looks good because Chrome and Firefox > have also the same behavior. > > Why Safari on iOS gives us mysterious results. Do you have any plan to fix? > > Thanks Thanks for the report! What specifically is the issue you'd like us to address? Can you maybe mark up the screenshot with the parts you aren't expecting? Or just include a screenshot of what you are expecting the website to look like?

pasta0915

Comment 7 2021-10-06 20:37:47 PDT

Comment on attachment 439342 [details] Screenshot taken by iPad native I have mistaken to make it obsolete

pasta0915

Comment 8 2021-10-06 20:38:34 PDT

Comment on attachment 439341 [details] Image taken by tabs.captureVisibleTab It is deprecated

pasta0915

Comment 9 2021-10-06 20:45:04 PDT

Created attachment 440464 [details] marked up area to expect I marked up the image area which expect to receive by captureVisibleTab. and I re-organize attachments

Kate Cheney

Comment 10 2022-03-30 12:48:08 PDT

Hi there! Thanks for reporting. This looks like a bug in Safari extensions, not WebKit. I passed it along to the right people, and you can also file a bug against Safari on https://feedbackassistant.apple.com/ if you'd like.

Note You need to log in before you can comment on or make changes to this bug.