- From: Nolan Lawson <notifications@github.com>
- Date: Tue, 06 May 2025 19:31:39 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 7 May 2025 02:31:43 UTC
nolanlawson left a comment (w3c/IndexedDB#130) Thank you for taking on this issue! I'm excited to see it finally resolved. 🎉 I haven't worked heavily with IndexedDB in a while, but since I opened this issue, I'd say my preference is for #<span></span>3 followed by #<span></span>1. I like #<span></span>3 because it's explicit and analogous to the APIs you mention (I'd toss `CSS.supports()` / `@supports` in that bucket). I also like that it opens the door for more sophisticated IDB query options that the API could support. The flaws with #<span></span>2 are what you mention, plus that adding a direction could cause confusion about what "upper" and "lower" mean (which is already tricky). #<span></span>4 is okay but a bit verbose. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/130#issuecomment-2856841012 You are receiving this because you are subscribed to this thread. Message ID: <w3c/IndexedDB/issues/130/2856841012@github.com>
Received on Wednesday, 7 May 2025 02:31:43 UTC