4 ms·

Web Share Target API (manifest: share_target) - it allows a website to specify itself as a share target. Of course, it's not yet supported on iOS.

JimDabell 3y ago
This is not a web standard. Google wrote the specification and only Google have implemented it. It’s an unofficial draft: > Editors: > Matt Giuca (Google Inc.) > Eric Willigers (Google Inc.) > Status of This Document > This specification was published by the Web Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track — https://w3c.github.io/web-share-target/level-2/ https://w3c.github.io/web-share-target/level-2/ Firefox doesn’t implement it either: https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 Apple raised a concern about spoofing which seems to have gone unaddressed by the spec authors in over a year: https://github.com/w3c/web-share-target/issues/109 https://github.com/w3c/web-share-target/issues/109 This may yet turn into a web standard given more work, but please don’t hold up a Google spec. implemented only by Google as if it were a part of the web platform that Apple are late in implementing.
- bensecure 3y ago
  The only relevant browsers on mobile are google's and apple's, and (modern) web standards are created by enough popular browsers implementing them. Literally all it would take for this to be a reliable web standard would be apple choosing to implement it.
  - FridgeSeal 3y ago
    Well until that point, and until it’s ratified as one, it’s not a web standard, so you can’t get disappointed that nobody else implements it.
  - JimDabell 3y ago
    You can apply that logic to literally anything Google thinks up. Google writes something in a spec and no matter how stupid, insecure, or privacy violating it is, by this logic Apple is now falling behind and holding the web back because all it would take to make it a standard is for Apple to do what Google wants. Why are you so keen to hand the web platform entirely over to Google?

JimDabell 3y ago

This is not a web standard. Google wrote the specification and only Google have implemented it. It’s an unofficial draft: > Editors: > Matt Giuca (Google Inc.) > Eric Willigers (Google Inc.) > Status of This Document > This specification was published by the Web Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track — https://w3c.github.io/web-share-target/level-2/ https://w3c.github.io/web-share-target/level-2/ Firefox doesn’t implement it either: https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 https://bugzilla.mozilla.org/show_bug.cgi?id=1476515 Apple raised a concern about spoofing which seems to have gone unaddressed by the spec authors in over a year: https://github.com/w3c/web-share-target/issues/109 https://github.com/w3c/web-share-target/issues/109 This may yet turn into a web standard given more work, but please don’t hold up a Google spec. implemented only by Google as if it were a part of the web platform that Apple are late in implementing.

bensecure 3y ago
The only relevant browsers on mobile are google's and apple's, and (modern) web standards are created by enough popular browsers implementing them. Literally all it would take for this to be a reliable web standard would be apple choosing to implement it.
- FridgeSeal 3y ago
  Well until that point, and until it’s ratified as one, it’s not a web standard, so you can’t get disappointed that nobody else implements it.
- JimDabell 3y ago
  You can apply that logic to literally anything Google thinks up. Google writes something in a spec and no matter how stupid, insecure, or privacy violating it is, by this logic Apple is now falling behind and holding the web back because all it would take to make it a standard is for Apple to do what Google wants. Why are you so keen to hand the web platform entirely over to Google?