-
Notifications
You must be signed in to change notification settings - Fork 9
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
Incubation status #25
Comments
This is not something we should archive, but instead, we should clearly mark it as "shipped in a single implementation" (or something along those lines). |
Apologies for the late response. Basically, what @yoavweiss said. This spec may be Dormant, but it isn't dead! There are some important open issues (#19, #4, and #24 are the highest on my list) but without feedback from implementers (both UAs, and other folks running servers/CDNs), I have abstained from bikeshedding my own answers, disconnected from any kind of consensus. IMO this spec is valuable to mark as not dead because it:
That all feels valuable, and if/when another browser implements Client Hints Infrastructure (which has been very active), I hope to advocate for this spec more actively. Open to any thoughts and I'll be keeping an eye on WICG/admin#138. |
Yes, agreed. Simply because responsive images is not fully solved yet, this proposal has value in providing a potential solution. |
I also agree that this proposal is really useful, and I'd like to see other browsers implement it. |
Hi @eeeps! Just checking for status on this incubation as it looks kinda dormant (not much activity for a few years).
Is this something you want to continue to pursue or should we archive this?
The text was updated successfully, but these errors were encountered: