Post

Rik Schennink
@rikschennink.com

Found this API under our Christmas tree. 🎁🎄 I'm currently appending a hidden <input type="file"> inside the <file-pond> custom element, but it looks like that's not needed. With ElementInternals I can turn <file-pond> into a full blown form element. 🚀 developer.mozilla.org/en-US/docs/W...

3 reposts22 likes

Alex Suzuki
@alexsuzuki.com

Neat. What‘s your „new API adoption strategy“? When I see Baseline: March 2023 I‘m a bit hesitant but positive in general and would probably adopt.

Rik Schennink
@rikschennink.com

If the answer to "Can I gracefully make this work if this API isn't available?" is "yes" then I don't care how modern it is. When the answer is "no" devs could in theory fallback to v4, or even a plain <input type="file"/>, if needed. I find adopting new CSS features is a lot more difficult.

Alex Suzuki
@alexsuzuki.com

Let me rephrase: at what point would you consider removing the fallback? I recently moved to the Web Audio API in favor of creating an <audio> tag for beep feedback on scan, and WebGL2.

Rik Schennink
@rikschennink.com

As this would be a breaking change (someone could be relying on the fallback) I think only if there is a very good reason. Perhaps if the fallback is the origin of lots of support tickets / is a big chunk of code.