WebNotificationsDispositionOfComments
Drafting the DispositionOfComments for the WebNotifications spec.
The WG received 16 comments during the Last Call period.
Comment from Marcos http://lists.w3.org/Archives/Public/public-web-notification/2013Sep/0002.html
5 comments from James Burke: http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0000.html
2 comments from PFWG: http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0001.html
6 comments from Frederick: http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0003.html
Comment from NARUSE Yui: http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0004.html
Comment from Jasper St. Pierre: http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0008.html
| Comment | Author | Editorial or substantive | Accept, reject, or defer | Rationale | Link | Status | Action |
|---|---|---|---|---|---|---|---|
| Location of Editor's Draft | Marcos Caceres | Editorial | Reject | Comment references WHATWG document which, while related to the W3C Editor's Draft, is not itself the Editor's Draft. | http://lists.w3.org/Archives/Public/public-web-notification/2013Sep/0002.html | Responded | None |
| Ability to pass data with the Notification | James Burke | Substantive | Defer | The API targets several different system notification services, not all of which allow associating data with notifications. We should consider this feature request for v2 of the API. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0000.html | Replied; OP never got back to us | None |
| General notification callback entry point | James Burke | Substantive | Reject | The onfoo events are consistent with the rest of the platform; removing semantically named and defined events for a generic callback makes coding to the API more confusing for Web developers. Both the existing API and the proposed API are equally "unreliable" in scenarios where the tab has been closed or the browser quit. How a system notification service re-launches your browser or causes a navigation back to your page is out of scope for this API. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0000.html | Replied; OP never got back to us | None |
| Fire only one event instead of onclick and onclose | James Burke | Substantive | Reject | Some system notification services support the concept of activating a notification, while others do not. This is why the spec currently states "In general, the event model for notifications is best-effort; while the Notification object offers a click event, applications may enhance their functionality by listening for that event, but cannot depend on receiving it, in case the underlying notification platform does not provide that capability." These events should remain separate. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0000.html (We should also pull in Anne's change that clarifies activation.) | Replied; OP never got back to us | None |
| onclick does not bring web app to front | James Burke | Substantive | Reject | How or even whether a system notification service exposes clicks to the Web Notification API is undefined. FirefoxOS's notifiction service is free per spec to adopt the behavior requested. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0000.html | Replied; OP never got back to us | None |
| Ability to set notification modes | James Burke | Substantive | Defer | Several system notification services (e.g. iOS) only provide per-app or per-device equivalents to the requested per-notification feature. If platforms with per-notification granularity of such settings become more prevalent, we should consider exposing that in the Web Notification API. That said, prematurely exposing such a feature may overconstrain our API's ability to match future platform APIs well. Also, as stated this seems really moble-centric; if we were to add an API, it should probably be more generic (e.g. priority numbers). | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0000.html | Replied; OP never got back to us | None |
| Unknown primary language violates WCAG | PFWG | Substantive | Reject | Concur with anne's rationale in http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0002.html | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0001.html | Replied | None |
| Alternative text for notification icon | PFWG | Substantive | Reject | The icon is decorative and provides no additional information. See the prior discussion at http://lists.w3.org/Archives/Public/public-web-notification/2012Jul/0000.html We should consider an editorial change to make this more clear. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0001.html | Replied | None |
| Interaction with touch | Frederick Hirsch | Editorial | Partially accepted | Concur with anne in http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0010.html (and we should pull in his editorial change which clarifies this.) | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0003.html | Accepted | None |
| Expand security and privacy text | Frederick Hirsch | Editorial | Reject | Concur with Anne's comments in http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0010.html | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0003.html | Accepted | None |
| It would help to clarify which specific terminology from DOM, HTML, IDL and URL is used (in Section 3), so it is clear when specific meanings are intended. | Frederick Hirsch | Editorial | Reject | Concur with Anne's comments in http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0010.html | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0003.html | Accepted | None |
| Model should state assumptions and constraints | Frederick Hirsch | Editorial | Reject | Concur with Anne's comments in http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0010.html System notification services have different constraints, so we should leave this undefined. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0003.html | Accepted | None |
| What happens when language is unknown? | Frederick Hirsch | Editorial | No change | Concur with Anne's comments in http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0010.html | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0003.html | Accepted | None |
| Are there any best practices/experiences related to tags that should be noted? | Frederick Hirsch | Editorial | No change | Concur with Anne's comments in http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0010.html | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0003.html | Accepted | None |
| Closing notifications when tab gets closed | NARUSE, Yui | Substantive | Reject | Some User Agents may want to keep notifications persistent after a tab has been closed, this restriction would prevent User Agents from such an implementation. Also some system notification services may not allow UAs to do this in the first place. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0004.html | Pinged and accepted | None |
| Add expiration time to notifications, UA should close when expiry time is reached | NARUSE, Yui | Substantive | Reject | Such a feature would require browsers to remember notifications that have been sent, which may be an unacceptable implementation burden on some system notification services. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0004.html | Pinged and accepted | None |
| instead of using live callbacks, have the user agent navigate to a specific URL in the originating tab / a new tab, which the web app could detect and do things on? | Jasper St. Pierre | Substantive | Reject | First of all, the platform may or may not keep track of the originating page already. Secondly, what happens after the user's browsing session on your page goes away (due to navigation, tab close, etc.) is out of scope. | http://lists.w3.org/Archives/Public/public-web-notification/2013Oct/0008.html | Pinged and accepted | None |
P.S. I hate MediaWiki table syntax so, so much.