Oh. Is there a potential solution?

I think so, but I'll tell you tomorrow when I'm not on my watch

Good night fellow Apple Watchian

Good night

good morning

The solution is:

  • add an api to get auth that doesn’t send the token in a header (mostly copy-pasting from the current auth api)

  • add a listener to the form to intercept the default behavior (posting to the original api) and instead post to the new api and then save the returned cookie in the browser using document.cookie (this works, I’ve tested)

  • But don’t change the form’s default behavior, so it’ll still work when javascript is disabled

@jeffalo

Nice! I can’t wait to be able to use the beta on AW (if Jeffalo gets to this)

The beta actually looks more Apple Watch friendly than wasteof2, because it has <dialog>s in many places instead of alerts

<dialog>?

some kind of modal at least, not alerts

the solution is that apple stops being difficult and just follows the web spec. its not for me to bend over backwards to support their dumb limitations

well it is the Apple Watch, which isn’t remotely intended to be a web browser

so why should i change my site to make it work on apple watches? if a browser can't support the most basic features that's not my fault.

It is very easy to change it though, just saying

View all comments