Layoutify-for-Instagram icon indicating copy to clipboard operation
Layoutify-for-Instagram copied to clipboard

Dimension of images opened with right-click context menu

Open Blazeflack opened this issue 4 years ago • 3 comments

From the description of this extension it seems that the highest quality image should be shown, but this is not the case.

When opening images through the right-click context menu, it is apparent that it is not the "highest quality" image that is being shown.

I have tried identifying the code responsible for using the highest quality image in order to attempt to fix it myself, but haven't been able to locate it. As such I will rely on this ticket instead :)

Observe the following post: https://www.instagram.com/p/B1BkIU2pZkT/

  • Using right-click context menu and "view image" will display an image with the dimensions 640x640.
  • By using the following javascript in console you get the actual highest quality image document.querySelectorAll('meta[property="og:image"]')[0].content

You can easily see the difference.

Any chance this can be corrected? Or perhaps allow a setting that will always use the actual highest quality image? :)

Blazeflack avatar Oct 23 '19 20:10 Blazeflack

When I right-click I get an image that is 1080x1080, really weird. document.querySelectorAll('meta[property="og:image"]')[0].content is undefined for me on that page.

Do you have any other extensions installed?

kurtextrem avatar Oct 27 '19 07:10 kurtextrem

Hi. Sorry about the late reply. For some reason I was not notified.

It looks like Instagram got rid of OpenGraph, so the previously mentioned way of getting the image of highest quality is now gone.

There is a different way to do it though. When you go to an Instagram post, you can append the following to the URL: media/?size=l

It will result in an URL like this: https://www.instagram.com/p/B1BkIU2pZkT/media/?size=l

To answer your question, I tested the issue with this extension enabled as the only one. This was tested on Google Chrome x64 version 78.0.3904.108

Is there anything I can do on my end to help debug it further?

Blazeflack avatar Nov 28 '19 02:11 Blazeflack

Can you enable chrome://flags/#enable-experimental-web-platform-features, restart your browser and tell me if it works afterwards? I would be surprised if this causes it to work, but that could be one reason

kurtextrem avatar Nov 28 '19 08:11 kurtextrem