New post on secure context #100
Conversation
✅ Deploy Preview for beautiful-dieffenbachia-e315ce ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| In our study, almost all of these are features that used to be standard but were then deprecated and removed from the specification: for example, [`PaymentAddress`](https://developer.mozilla.org/en-US/docs/Web/API/PaymentAddress). Perhaps it's not so important to display secure context information for these. | ||
|
|
||
| However, nonstandard features are generally a problem for any broader attempt to use Web IDL as a data source. It's been suggested that we could extract the browser-specific IDL and make a nonstandard companion to the webref/idl package. |
There was a problem hiding this comment.
Great post! Note that the discussion on SecureContext in IDL is leading to some further interesting findings in webref
Just a note on this particular proposal that if OWD/MDN are willing to maintain the data, I think we would be happy to have this integrated in some way in webref (since that's likely something other webref consumers would find useful)
|
Awesome write up, and great to shout-out to Onkar. I guess my only question is whether there are any other contributors/team members/mdn friends to acknowledge as having been helpful with this study? |
I'm totally happy to add acknowledgements if anyone can think of any that I have missed. Apart from Onkar the obvious is webref, which I have also mentioned in the post. |
pages/content/posts/securecontext-webidl/securecontext-webidl.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Florian Scholz <fs@florianscholz.com>
No description provided.