- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 03 Mar 2025 02:06:02 -0800
- To: w3c/push-api <push-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 3 March 2025 10:06:06 UTC
@annevk commented on this pull request. > + </dt> + <dd> + <p> + A boolean. + </p> + </dd> + <dt> + <code>silent</code> + </dt> + <dd> + <p> + A boolean. + </p> + </dd> + <dt> + <code>require_interaction</code> > (If the casing was same the parsing step could just say "parse it as NotificationOptions" after extracting title first. And then updating notification options wouldn't require updating both specs.) This would diverge too much from the standard JSON processing model so I don't think we should do that. But I think we can align on the casing here. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/push-api/pull/385#discussion_r1977224614 You are receiving this because you are subscribed to this thread. Message ID: <w3c/push-api/pull/385/review/2653643530@github.com>
Received on Monday, 3 March 2025 10:06:06 UTC