tantek.com

t

  1. Note that since this issue was opened, the spec was adopted by the Web Apps WG, and published as a W3C Recommendation as of 2023-05-30:
    * https://www.w3.org/TR/2023/REC-web-share-20230530/

    Updated latest editor’s draft AKA
    * Specification or proposal URL: https://w3c.github.io/web-share/

    Dropping label "position:positive" until we resolve the conflicts between negative, neutral, and positive historical comments upthread, to avoid miscommunicating our position (which is semi-orthogonal to any implementation status — see individual bugs cited above for that).

    on
  2. Re-opening this due to unresolved comments (mix of negative, neutral, positive), and substantial new information about the UI that current implementations are presenting as of 2025.

    Previously, previously, previously:
    * 2018-01-10 https://github.com/mozilla/standards-positions/issues/27#issuecomment-356793352 “harmful”
    * 2018-01-10 https://github.com/mozilla/standards-positions/issues/27#issuecomment-356784523 “pour more fuel on the centralization”
    * 2017-12-18 https://github.com/mozilla/standards-positions/issues/27#issuecomment-352661649 “lowers friction purely for content silos … bad for the web.”

    And a minor unaddressed concern from Martin:
    * 2018-11-08 https://github.com/mozilla/standards-positions/issues/27#issuecomment-437243973 “Giving sites the ability to share something else reduces the incentive to set window.location to something usable”

    Since those concerns were written (validated by screenshots at the time showing centralized content / social media silos in browser UI), it appears browsers (perhaps OS updates) no longer show such silos in browser UI for “share” (as of 2025).

    Need updated screenshots.

    on