Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support high DPI image assets on the extension store #240

Closed
hanguokai opened this issue Jul 9, 2022 · 2 comments
Closed

Support high DPI image assets on the extension store #240

hanguokai opened this issue Jul 9, 2022 · 2 comments

Comments

@hanguokai
Copy link
Member

hanguokai commented Jul 9, 2022

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)

  • Edge: 300x300
  • Chrome: 128x128
  • Firefox: 32x32 and 64x64, also support svg.

Screenshots

  • 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.

@xeenon
Copy link
Collaborator

xeenon commented Jul 24, 2022

As mentioned in the last meeting, extension store issues are out-of-scope in this group.

@xeenon xeenon closed this as completed Jul 24, 2022
@xeenon xeenon reopened this Jul 24, 2022
@xeenon xeenon closed this as not planned Won't fix, can't repro, duplicate, stale Jul 24, 2022
hanguokai added a commit to hanguokai/webextensions that referenced this issue Jul 24, 2022
As w3c#240 , extension store issues are out-of-scope.
@hanguokai
Copy link
Member Author

I create a PR to add "Extension stores are out-of-scope" in Charter. So community members can know that in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants