Skip to content

Editorial: remove Extensibility text #239

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

Merged
merged 3 commits into from
Jul 7, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 0 additions & 50 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -688,56 +688,6 @@ <h2>
</li>
</ul>
</section>
<section class="appendix informative">
<h2>
Extensibility of this API
</h2>
<p>
The Web Share API is designed to be extended in the future by way of
new members added to the {{ShareData}} dictionary, to allow both
sharing of new types of data (<i>e.g.</i>, <a href=
"https://github.com/w3c/web-share/issues/12">images</a>) and strings
with new semantics (<i>e.g.</i> author).
</p>
<div class="warning">
This doesn't mean user agents can add whatever members they like. It
means that new members can be added to the standard in the future.
</div>
<p>
The three members {{ShareData/title}}, {{ShareData/text}}, and
{{ShareData/url}}, are part of the base feature set, and
implementations that provide {{Navigator/share()}} need to accept all
three. Any new members that are added in the future will be
<em>individually feature-detectable</em>, to allow for
backwards-compatibility with older implementations that don't recognize
those members. These new members might also be added as optional "MAY"
requirements.
</p>
<div class="note">
There is <a href="https://github.com/heycam/webidl/issues/107">an open
discussion</a> about how to provide feature-detection for dictionary
members. Web Share will use the mechanism produced by that discussion.
</div>
<p>
The {{Navigator/share()}} method returns a rejected promise with a
{{TypeError}} if none of the specified members are present. The
intention is that when a new member is added, it will also be added to
this list of recognized members. This is for future-proofing
implementations: if a web site written against a future version of this
spec uses <em>only</em> new members (<i>e.g.</i>,
`navigator.share({image: x})`), it will be valid in future user agents,
but a {{TypeError}} on user agents implementing an older version of the
spec. Developers will be asked to feature-detect any new members they
rely on, to avoid having errors surface in their program.
</p>
<p>
Editors of this spec will want to carefully consider the genericity of
any new members being added, avoiding members that are closely
associated with a particular service, user agent or operating system,
in favour of members that can potentially be applied to a wide range of
platforms and targets.
</p>
</section>
<section id="conformance"></section>
<section id="idl-index"></section>
<section class="informative">
Expand Down