Able to reproduce the issue using #66.0.3350.0 on Android Pixel 8.1. This issue seems to reproducible using on weak Internet connection.

Requesting UI>Browser>Mobile for further triaging of the issue.

Thanks!!

Is this a regression?

This issue is reproducible intermittently using latest Chrome Canary versions on Pixel 8.1 as this issue is only seen on enabling open new context menu (enabled in chrome://flags) on using slow networks.

Hence removing Needs-Bisect label for now and add it back if required.

Thanks!!

Hm, I'm not sure I see a big problem with this – this is what the image looks like to the web page, and seeing the size could be quite useful. To me, the biggest annoyance is maybe that the image gets scaled down, so the text becomes less readable.

(assigned to sandeepkumars for more clarification)

+1 to what bauerb mentioned - I'm not sure I fully understand what the problem is here.

If the user's on a slow network, and has Data Saver enabled, then the user should see LoFi image placeholders instead of the full images on the page, along with an option to load in the full versions of all the images on the page (via the infobar that shows up at the bottom of the screen, i.e. "Show original"), and the context menu even has a "Load image" option that will load in the full version of the image.

OK, if we discuss about images I will be more generic:

We can have few states with images and we have few issues:

1. image recognized, not loaded - this bug (I think, that preview shouldn't be displayed or image size should be definitely much bigger)

2. image recognized, low resolution (I think LoFi) - https://bugs.chromium.org/p/chromium/issues/detail?id=806606 (visible at least some ago)

3. image recognized, normal resolution - few bugs related to scaling (IMHO, we should use normal size or allow for pinching for resizing preview)

4. image recognized, incorrect - tab crash (https://bugs.chromium.org/p/chromium/issues/detail?id=799762)

5. image not recognized, although should be - two bugs (vector one or created in CSS)

6. image loaded, but "sad" image in preview - https://bugs.chromium.org/p/chromium/issues/detail?id=794243

7. image recognized, totally correct, but withouth preview - https://bugs.chromium.org/p/chromium/issues/detail?id=793581 (fixed)

Thanks for the clarification, I think I understand better now.

LoFi image placeholders are the translucent gray boxes with text in them displaying the estimated full resource size (i.e. in bytes) of the image. If I understand correctly, It looks like what's happening is that the user (with the Data Saver setting enabled) browses a page on a slow network, and images on that page are replaced with these translucent gray box placeholder images, which is how the LoFi feature works.

If I understand correctly, this bug report is about whether or not the "Image" tab in the context menu should show a preview when the image has been replaced with a translucent gray box placeholder image by LoFi.

Since the translucent gray box image in the context menu preview is the same as what the user sees on the page, then I think this is working as intended.

I agree with bauerb@ that the scaling makes it hard to read the text in the image. It sounds like the wonky scaling problems affect regular images as well as LoFi placeholder images though, so that sounds like a separate bug.

Feel free to reopen this if I've missed anything, or if I'm misunderstanding the bug that you're describing here.