-
Notifications
You must be signed in to change notification settings - Fork 162
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
Please add caption property to screenshots #773
Comments
We are actually considering dropping screenshots entirely (and metadata that would be ingested by stores). These fields didn't end up getting used anywhere and are obviously not used by browsers. |
I hope not, we didn't even know about screenshots until a week ago and I'm sure a lot of other developers don't know about it. The popular tutorials and PWA blogs/articles don't mention it -- a well kept secret. |
Kinda a good thing then... less damage if we do remove it. Again, the problem is lack of support from anyone that we know of... although, we need to check with the Microsoft Store, as these requests came from them I think (but not sure if they ever added support or not). |
@aarongustafson, do you know what the story is with |
I cant speak to the level of detail about this that Aaron can, but wanted to add my 2 cents that I do know that screenshots are important to us at Microsoft for our store experience. Also, speaking for my team at least at Microsoft, we have been experimenting with screenshots and want to start publicizing them more as a useful way to improve even the default install experience in browsers like Chrome and the new Edge. |
Yep, I'll echo what @jgw96 said. We do use screenshots for the Store currently and are actively investigating ways to make that (and categories, etc.) more visible to end users within a browser context. |
Specifically, does Edge actually parse the screenshot member and extract detail from it? It would be good to know the specific level of support for this member you have. :) |
@dominickng We are not currently using it in Edge though, as @jgw96 said, we are experimenting with them in the context of Edge. We are actively using the key in the Microsoft Store. Other PWA "app stores" are also including screenshots as well (e.g., AppScope, PWA Store, etc.). This seems like an area that is still growing and being explored. As evidenced by @SpeednetGroup’s comment, many devs don’t know it exists—perhaps because the Google docs don’t include it?—and I suspect as PWAs show up in more traditional "app stores" this key will become more valuable. For context of how we are using
To @SpeednetGroup’s original point, I agree that a |
@aarongustafson, that's really exciting to hear it's being used! We were a little worried that it wasn't - so definitely keep in the spec then. Then yes, I agree that having a description of the image makes sense. |
Open to discussing this @ TPAC today or tomrrow. |
Closing in favor of w3c/image-resource#7 |
Since
screenshots
is intended to be used by app stores, and because all app stores use textual captions associated with each screenshot, we need to add acaption
(or perhapsdescription
) string property to each screenshot object.As it stands right now, you can just define a bunch of screenshots that will get displayed in an app store without any context or description.
Of course,
caption
can be an optional property.The text was updated successfully, but these errors were encountered: