We’re crying at a pretty high level IMO. So many cool APIs are available now in all browsers that enable us to build things that used to be impossible on the web.
So don’t only focus at what isn’t here yet.
iOS404
51–60 of 101 posts
Re: iOS404
#52Off topic: We don't have missing people on milk cartons here in Europe. Seeing them always reminds me of being a teenager, watching Blur's Coffee and TV music video on MTV: https://www.youtube.com/watch?v=6oqXVx3sBOk
I don’t think I’ve ever seen a missing person on a milk carton in the US either. It is only something I’ve seen in TV and movies, and I’m in my 40s. My assumption is that this was a thing from the 1950s, but someone who grew up during that era would have to speak to it. I suppose it’s also possible it was a regional thing and I wasn’t in a region that did it.
Re: iOS404
#53The list doesn't tell the full story though, my biggest problem with it is that it's overall a buggy browser. I've encountered bugs on localStorage & indexDB, forms, SVG and CSS overflow, buggy border radius on videos (not sure if this one is fixed now) all of those being very basic web features.
I feel like they lack a lot in the QA side of things, it doesn't feel very polished.
I'd be more accepting of Safari if it would be more polished and had a better release cycle (it's also the last major non-evergreen browser), all the next gen features are good sure, but not a replacement for those problems.
Re: iOS404
#54The one browser API I wish every browser would support is the File System Access API. Because with it, we can offer users to hold their data natively on their devices. Instead of storing everything in the cloud. So far, I think only Chrome on the desktop supports it. Here is a nice demo: https://googlechromelabs.github.io/text-editor/ A text editor that works just like a native application.
You can check why Mozilla and Apple have opted to not support this.
https://github.com/mozilla/standards-positions/issues/154
https://github.com/WebKit/standards-positions/issues/28
Neither Mozilla or Webkit are satisfied that the proposal is safe by default, and contains footguns for the user that can be pretty destructive.
Re: iOS404
#55[flagged]
Its up to us developers to stop using functions only provided by one browser.
I find it absolute madness that anyone would use an API in their code which is only available on Chrome. If its not a standard which is not supported by the 4 main browsers, then its not going in my code.
Re: iOS404
#56We’re crying at a pretty high level IMO. So many cool APIs are available now in all browsers that enable us to build things that used to be impossible on the web. So don’t only focus at what isn’t here yet.
If problems aren’t called out they can’t be solved.
Re: iOS404
#57How iOS would support `::selection` with the tap-based interface?
Same for the CSS3 Cursor properties, doesn't make much sense on a touch-based device.
Re: iOS404
#58[deleted]
Re: iOS404
#59The one browser API I wish every browser would support is the File System Access API. Because with it, we can offer users to hold their data natively on their devices. Instead of storing everything in the cloud. So far, I think only Chrome on the desktop supports it. Here is a nice demo: https://googlechromelabs.github.io/text-editor/ A text editor that works just like a native application.
You can check why Mozilla and Apple have opted to not support this. https://github.com/mozilla/standards-positions/issues/154 https://github.com/WebKit/standards-positions/issues/28 Neither Mozilla or Webkit are satisfied that the proposal is safe by default, and contains footguns for the user that can be pretty destructive.
And what are they suggesting to improve the proposal? Apple, which makes $20B a year with Safari, surely has enough resources to make a counter-proposal?
Re: iOS404
#60Earlier quoted context omitted.
Me too. Device orientation, USB, Bluetooth, vibration, they don't belong in a web app.
All the dangerous ones come with comprehensive permissions prompts, and browsers can offer options for don't ask again/never ask etc, so if you're not interested there's still little downside to those being available for those who are. Personally, I've found a bunch of these super useful, as user and a developer. Being able to use tools like https://www.espruino.com/ide/ to play with hardware straight from the web is…
I would guess that most regular users are very quick to click “Allow” on a dialog box. I like how macOS handles unidentified apps where you have to navigate manually to the security settings to allow an unidentified app.