Sorry Safari team
We shared some incorrect data at Chrome Dev Summit. Here's my apology and what lead to the mistake.
I love the web. The web should allow anyone to access any experience that they need without the need for native install or content walled garden.
We shared some incorrect data at Chrome Dev Summit. Here's my apology and what lead to the mistake.
I'm currently building a simple CRUD client-side only data logger PWA that contains no client-side JavaScript apart from what is inside the service worker. To do that I am following basic REST principles, and just using the Form element to submit data to the service-worker that then stores in it IndexedDB and renders the results back out to the client. I will explain more in another post, but in this post I want to quickly document how I fixed an issue in Safari.
I love view-source, it's a nifty super power of the web that nearly all mobile browsers are trying to kill. Not exactly sure why. View-source is what got me into web development because I could see how other people structured their pages, and at the time I started web development it was pretty much the only way to debug web pages. I've also been using my iPad Pro whilst I am not at work for the next month or so.
Ricky Mondello over on the Safari team just recently shared a note about how Twitter is using the ./well-known/change-password spec. I just noticed that Twitter has adopted the Well-Known URL for Changing Passwords! Is anyone aware of other sites that have adopted it? Twitter's implementation: https://twitter.com/.well-known/change-password Github's: https://github.com/.well-known/change-password Specification :https://github.com/WICG/change-password-url Read full post. The feature completely passed me by but it is a neat idea: given a file in a well-known location, can the browser offer a UI to the user that allows them to quickly reset their password without having to navigate the sites complex UI.