-
Notifications
You must be signed in to change notification settings - Fork 62
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
IDBKeyRange.includes or IDBKeyRange._includes? #270
Comments
The method is See: https://heycam.github.io/webidl/#idl-names Per #226 bikeshed should handle this... seems like there's still a glitch somewhere in the cross-linking though. |
Might as well use this to track linking. Not sure what's going on yet. whatwg/webidl#733 indicates the BS docs are wrong, at least... |
Ah, interesting. Never came across that before. Good to know that that is a thing... |
Bikeshed issue: speced/bikeshed#1489 In the Indexed DB 2.0 spec a note was slipped below the IDL fragment in which explained this: https://www.w3.org/TR/IndexedDB-2/#idbkeyrange That was done during the final review, didn't make it into 3.0. I'll copy it. |
"includes" is reserved word in WebIDL, so a method with that name needs to be escaped with a leading underscore in IDL fragments. This confuses Bikeshed (speced/bikeshed#1489) so manually correct the link. Also, the 2.0 version of the IDB spec had a note which gave context for this; transplant that to the 3.0 version. Resolves #270
"includes" is reserved word in WebIDL, so a method with that name needs to be escaped with a leading underscore in IDL fragments. This confuses Bikeshed (speced/bikeshed#1489) so manually correct the link. Also, the 2.0 version of the IDB spec had a note which gave context for this; transplant that to the 3.0 version. Resolves #270
"includes" is reserved word in WebIDL, so a method with that name needs to be escaped with a leading underscore in IDL fragments. This confuses Bikeshed (speced/bikeshed#1489) so manually correct the link. Also, the 2.0 version of the IDB spec had a note which gave context for this; transplant that to the 3.0 version. Resolves #270
The IDL defines a
_includes()
methods, but then there is an algorithm/description for anincludes()
method. Which one is it supposed to be?The text was updated successfully, but these errors were encountered: