Skip to content
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

Changed to allow site-triggered prompt without defaulting to automatic prompt #584

Merged
merged 11 commits into from Jun 8, 2017

Conversation

mgiuca
Copy link
Collaborator

@mgiuca mgiuca commented Jun 7, 2017

Closes #576


Preview | Diff

@mgiuca mgiuca requested a review from marcoscaceres June 7, 2017 07:31
@mgiuca
Copy link
Collaborator Author

mgiuca commented Jun 7, 2017

index.html Outdated
@@ -396,21 +396,36 @@
Install prompts
</h2>
<p>
An end-user can <dfn data-lt="manual installation">manually</dfn>
There are three ways that the installation process can be triggered:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe change this to "multiple ways" instead of "three"... always forget to update those numbers when new things get added.

Copy link
Member

@marcoscaceres marcoscaceres left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 Just a couple of little things. Looking good.

index.html Outdated
<li>The <a>installation process</a> can occur through a
<dfn>site-triggered install prompt</dfn>: the site can
programmatically request that the user agent present an install
prompt to the user. The availability of this feature may be
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/The availability of this feature may be/The user agent MAY restrict the availability of this feature/

index.html Outdated
MUST run the <a>steps to notify before an automated install
prompt</a>.
MUST run the <a>steps to notify that an install prompt is
available</a>, to give the site the opportunity to suppress the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should say, instead of "to give the site the opportunity to suppress the install prompt" something like "prevent the default action (which is to install the application)". That would maybe align better with . preventDefault()

index.html Outdated
prompt</a>.
MUST run the <a>steps to notify that an install prompt is
available</a>, to give the site the opportunity to suppress the
install prompt. Alternatively, the user agent may run the <a>steps to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/may/MAY

index.html Outdated
<div class="note">
The <code>beforeinstallprompt</code> event is somewhat misnamed, as
it does not necessarily signal that an <a>automated install
prompt</a> will follow (depending on the user agent, it may just be
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/it may just/it can just
or "it might just"
(avoid RFC2119 keywords in notes... even in lowercase)

index.html Outdated
discretion (rather than prompting at an arbitrary time), whilst
still providing a prominent UI to do so.
prompt from showing until the user clicks a button to show a
site-triggered install prompt. In this way, the site can leave
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: link back to def <a>site-triggered install prompt</a>

@marcoscaceres
Copy link
Member

marcoscaceres commented Jun 7, 2017

@mgiuca, just FYI, we added a magic service that generates previews/diff for us. It adds the links at the top of the Pull Request.

screenshot 2017-06-07 18 19 05

(PS: if you want it for Web Share, just copy this file to that repo: https://github.com/w3c/manifest/blob/gh-pages/.pr-preview.json and make any changes needed. Should be straight forward)

@marcoscaceres
Copy link
Member

*FYI

@mgiuca
Copy link
Collaborator Author

mgiuca commented Jun 8, 2017

Done all of those. Thanks for the review.

Whoa, the pr-preview is magical. Trying it on Web Share.

@mgiuca mgiuca merged commit 7a8184e into w3c:gh-pages Jun 8, 2017
@mgiuca mgiuca deleted the allow-only-manual-prompts branch June 13, 2018 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants