-
Notifications
You must be signed in to change notification settings - Fork 312
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
Rewriting abstract #1494
Rewriting abstract #1494
Conversation
@jungkees @slightlyoff @mattto any thoughts about this before I merge? |
It seems to me that the first paragraph of the change seems a bit too specific in using terms. I think abstract should just explain what it is simply. In that regard, the original text reads easier. To @annevk's point, I'll leave a comment in the issue. |
I'm OK with this PR. Happy to take another look if you incorporate @jungkees's suggestions too. |
Hmm, I was trying to describe what the service worker is before things like the fetch event are added on top, and why it's used for particular event rather than just firing events in . a document. Eg, I could remove some of the terms & make it: The core of this specification is a worker that wakes to receive events. This provides an event destination that can be used when other destinations would be inappropriate, or no other destination exists. Is that better? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got your point. It looks good to me. Thanks for addressing my comment.
Fixes #1493
Preview | Diff