6 ms·
Of undocumented Chrome features and unreadable W3C specs
- hannibalhorn 12y agoOf course, ideally there'd be documentation, but this particular change seems pretty obvious, no? The first argument used to be a TEMPORARY or PERSISTENT constant, but now there are separate instances for temporary or persistent and you no longer specify the constant, as it'd be redundant.
- awalGarg 12y agoJust because it is obvious doesn't mean "no docs" is ok. A high level API like this needs documentation for every function exposed. Reasons covered in the article.
- _ZeD_ 12y agowhat about mdn? https://developer.mozilla.org https://developer.mozilla.org
- slater 12y ago> I searched for queryUsageAndQuota and found … nothing. No documentation, no code example. No way of figuring out what the first argument should be. Umm... first few hits both on DDG _and_ Google point to https://developer.chrome.com/apps/offline_storage#managing_quota https://developer.chrome.com/apps/offline_storage#managing_q... which contains documentation _and_ code examples
- MadcapJake 12y agoThat's the deprecated version and example that he specifically talks about in the article..
- slater 12y agoerr... oh. :)
- bshimmin 12y agoI think someone really needs to give PPK a hug. He's done a great job over the years with his work on QuirksMode, but reading his blog these days I mostly just feel sorry for the poor guy!
- aboodman 12y agoIt would be possible to generate basic API documentation from the IDL the browsers actually use internally. It would not necessarily be completely accurate because sometimes browsers don't use IDL for their features, but it would be another tool, and would have helped in this case. You wouldn't need to even be a member of the browser team to do this, since the relevant data is all open source.