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

Notifications API: inline replies #91

Open
annevk opened this issue Jun 4, 2018 · 5 comments
Open

Notifications API: inline replies #91

annevk opened this issue Jun 4, 2018 · 5 comments
Labels
proposal appears stale venue: WHATWG Specifications in a WHATWG Workstream

Comments

@annevk
Copy link
Contributor

annevk commented Jun 4, 2018

Explainer: https://github.com/anitawoodruff/inline-notification-replies

Standard PR: whatwg/notifications#132
HTML diff of that: https://whatpr.org/notifications/132/e9407eb...e308162.html

Since we don't have anyone actively maintaining the Notifications API, I figured I'd escalate this here.

I suspect we're either defer (minus myself, since I have helped with review) or worth prototyping.

@martinthomson
Copy link
Member

This looks like an OK feature, but I think that it might be a little too low level a question for this repo. It's a tiny feature. Not sure that it makes sense to ask questions here at this level of detail.

Separately, I'm not sure that the proposed process for backward compatibility (treat these as simple buttons) works; some process for feature detection would seem to be necessary.

@annevk
Copy link
Contributor Author

annevk commented Jun 4, 2018

@martinthomson yeah, so what is the place for minor features? I'd rather not make the call alone on behalf of Mozilla as that feels somewhat conflict-of-interesty if I also help maintain the standard and for a number of things we don't have a clearly identified owner. (And even when there's a clearly identified owner it can be hard to get them to comment on the relevant GitHub issue.)

@ekr
Copy link
Contributor

ekr commented Jun 5, 2018

I'm less concerned with minor versus major than whether it fits into some broader set of APIs we are going to want; if so, it would be better to figure out the overall architecture

@dbaron dbaron added the venue: WHATWG Specifications in a WHATWG Workstream label Aug 9, 2018
@dbaron
Copy link
Contributor

dbaron commented Nov 30, 2018

Who would be likely to implement this if we were going to do so? Maybe they would have feedback.

That said, it seems like a reasonable feature to me, so I'm fine with just marking as worth prototyping.

@dbaron
Copy link
Contributor

dbaron commented Nov 30, 2018

That said, I'm also not entirely sure how to list this in the overall positions table, given that it's a feature within a spec...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal appears stale venue: WHATWG Specifications in a WHATWG Workstream
Projects
Development

No branches or pull requests

4 participants