4 ms·

> The only real problem is that you can’t feature-detect share_target support I didn't know this existed, so the first thing I did is check the caniuse website

> The only real problem is that you can’t feature-detect share_target support I didn't know this existed, so the first thing I did is check the caniuse website, and yeah not even they have info about the Web Share Target API[1][2]. As of writing this comment, they only have info about the Web Share API[3]. [1]: https://github.com/Fyrd/caniuse/issues/4670 https://github.com/Fyrd/caniuse/issues/4670 [2]: https://github.com/Fyrd/caniuse/issues/4906 https://github.com/Fyrd/caniuse/issues/4906 [3]: https://caniuse.com/web-share https://caniuse.com/web-share

troupo 1y ago
Because as with many, many, many APIs that Chrome ships it's not a spec: - there's a giant banner on the left saying "unofficial" - The "Status of this document" section states the following: --- start quote --- This document is a draft of a potential specification. It has no official standing of any kind and does not represent the support or consensus of any standards organization. --- end quote --- But just because it was shipped in Chrome and has some napkin scribbles resembling an official spec, people will both claim it's a spec and expect everyone to implement it.
chrismorgan 1y ago
Links on support: https://github.com/mdn/browser-compat-data/blob/main/manifests/webapp/share_target.json https://github.com/mdn/browser-compat-data/blob/main/manifes... (data integrated into the MDN page I linked) Chromium: https://chromestatus.com/feature/5662315307335680 https://chromestatus.com/feature/5662315307335680, implemented on Android from M71 and desktop from M89. WebKit: standards position is neutral <https://github.com/WebKit/standards-positions/issues/11 https://github.com/WebKit/standards-positions/issues/11>, and https://bugs.webkit.org/show_bug.cgi?id=194593 https://bugs.webkit.org/show_bug.cgi?id=194593 shows plenty of developer interest but doesn’t look to have been touched by Apple. Firefox: standards position is positive <https://mozilla.github.io/standards-positions/#web-share-target https://mozilla.github.io/standards-positions/#web-share-tar...>, but https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 has languished.

troupo 1y ago

Because as with many, many, many APIs that Chrome ships it's not a spec: - there's a giant banner on the left saying "unofficial" - The "Status of this document" section states the following: --- start quote --- This document is a draft of a potential specification. It has no official standing of any kind and does not represent the support or consensus of any standards organization. --- end quote --- But just because it was shipped in Chrome and has some napkin scribbles resembling an official spec, people will both claim it's a spec and expect everyone to implement it.

chrismorgan 1y ago

Links on support: https://github.com/mdn/browser-compat-data/blob/main/manifests/webapp/share_target.json https://github.com/mdn/browser-compat-data/blob/main/manifes... (data integrated into the MDN page I linked) Chromium: https://chromestatus.com/feature/5662315307335680 https://chromestatus.com/feature/5662315307335680, implemented on Android from M71 and desktop from M89. WebKit: standards position is neutral <https://github.com/WebKit/standards-positions/issues/11 https://github.com/WebKit/standards-positions/issues/11>, and https://bugs.webkit.org/show_bug.cgi?id=194593 https://bugs.webkit.org/show_bug.cgi?id=194593 shows plenty of developer interest but doesn’t look to have been touched by Apple. Firefox: standards position is positive <https://mozilla.github.io/standards-positions/#web-share-target https://mozilla.github.io/standards-positions/#web-share-tar...>, but https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 has languished.