Cordova’s whole deal was to implement draft Web APIs using their official JS APIs, but built natively, communicated to through WebView bridge features (WKWebView). In a way, Cordova (and Capacitor, though its goal isn’t to implement draft specs), are just browsers w more APIs.
-
-
Cordova features didn't need to hold themselves to the same semantics bar. The design language there wasn't WebIDL, and doing a slightly different thing was OK...the developer was entirely awares, after all. Not so on the web. Everywhere we diverge from spec is a bug. [7/N]
-
For all of these reasons, plus unease w/ adding a broken browser to ecosystem, I recommended we steer away from this approach. A tough call, but Apple must be on notice. We see the damage they're causing and won't paper over it while having to play by unfair rules. [FIN]
- 5 more replies
New conversation -
-
-
Makes sense! Thanks for the detail
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.