You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if the question (non-policy issue) about the extension store can be discussed here, but there's no doubt that developers care. For example, the image assets in the store listing page. Here I focus on supporting high-resolution images on the extension store, i.e. the size of the icon(logo), screenshots and promotional images(tiles), or support svg files.
CWS currently only accepts 1280x800 or 640x400 images for screenshots. This is a bad user experience on a hi-dpi screens.
Edge store is the same with CWS, but it shows screenshots more clearly, and user can click to view the big picture.
Firefox is also 1280x800. For other image sizes, we recommend using the 1.6:1 ratio.
In 2022, the extension store should support image assets for hi-dpi screen. For example, if screenshots's aspect ratio is 1.6, it should accept 640x400, 1280x800, 1920x1200, 2560x1600 screenshots.
Promotional images
Small tile: 440x280 pixels. I usually only provide this size of the promotional image.
The text was updated successfully, but these errors were encountered:
I'm not sure if the question (non-policy issue) about the extension store can be discussed here, but there's no doubt that developers care. For example, the image assets in the store listing page. Here I focus on supporting high-resolution images on the extension store, i.e. the size of the icon(logo), screenshots and promotional images(tiles), or support svg files.
Ref links:
Icon (Store logo, Manifest icons)
Screenshots
In 2022, the extension store should support image assets for hi-dpi screen. For example, if screenshots's aspect ratio is 1.6, it should accept 640x400, 1280x800, 1920x1200, 2560x1600 screenshots.
Promotional images
Small tile: 440x280 pixels. I usually only provide this size of the promotional image.
The text was updated successfully, but these errors were encountered: