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
The WebApps WG would welcome your review of the Web Share API specification. This is a delayed request for review after the FPWD was published in December 2019.
We hope you can complete your review before the end of October 2020, but if this timetable does not work for you, please let us know.
If you have comments or concerns with the Web Share API specification, please file them as issues on the Web Share API repository, and use the i18n-needs-resolution label.
I have reviewed this document and the self-review checklist. The only issue I found was that the text and title members can't be associated with language and (base) direction metadata (or label language/direction changes inline). In the self-review it is mentioned that "sharing rich text (such as HTML markup) as the content of text or one of the files is possible, if the sharing web site and share target support it, and would allow language association", but IIUC text and title might not end up with being displayed in an HTML/XML/etc. context.
We already have an issue for that, so I think we can continue to discuss in that issue: w3c/web-share#6
The WebApps WG would welcome your review of the Web Share API specification. This is a delayed request for review after the FPWD was published in December 2019.
We have completed the self-review checklist.
We hope you can complete your review before the end of October 2020, but if this timetable does not work for you, please let us know.
If you have comments or concerns with the Web Share API specification, please file them as issues on the Web Share API repository, and use the i18n-needs-resolution label.
Thank you.
@marcoscaceres @mgiuca @ewilligers
The text was updated successfully, but these errors were encountered: