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

Document considered alternatives #378

Closed
inexorabletash opened this issue Aug 11, 2020 · 2 comments
Closed

Document considered alternatives #378

inexorabletash opened this issue Aug 11, 2020 · 2 comments
Assignees
Labels
EyeDropper Issues relating to the EyeDropper API

Comments

@inexorabletash
Copy link

inexorabletash commented Aug 11, 2020

Great job on the EyeDropper API explainer. Over on Chrome we've definitely got partners who have requested web platform support for this use case.

I made a different proposal for the same feature over at whatwg/html#5584 - it would be good for this explainer to call out that alternative, and discuss the trade-offs that led to the current proposal. It is cool to see a different take on this, and I'm excited by what this approach to the API opens up.

Note that I'm very explicitly not advocating for my proposal over this. Having alternatives called out and compared makes for a strong explainer, and proactively heads off later "what about...?" conversations.

@inexorabletash inexorabletash added the EyeDropper Issues relating to the EyeDropper API label Aug 11, 2020
@BoCupp-Microsoft
Copy link
Contributor

Thanks for the issue. I've pushed an update to the explainer to call out the original proposal and our rationale in creating a new interface. Please take a look.

@inexorabletash
Copy link
Author

Looks good, thanks!

Another Googler also mentioned: "the more direct JS API likely seems ergonomically better for developers"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EyeDropper Issues relating to the EyeDropper API
Projects
None yet
Development

No branches or pull requests

2 participants