61–70 of 101 posts
so basically if an app can be ported as a web app, safari in ios won't support it? seems.....convenient
Earlier 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…
The browser (agent) is a native app designed to allow users to access and navigate web resources (we call them pages or documents). Pages can be styled (CSS) and made interactive (JavaScript).
When one wants to create an experience which goes beyond the scope of the browser, one builds another native app that is able to leverage the needed resources. A dedicated native app can embed a browser (e.g. webframe) or consume web resources through other protocols. A native app can also request access to hardware resources via the OS.
This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries from https://mozilla.github.io/standards-positions/ and https://webkit.org/standards-positions/ This is a good example of how the chromium monoculture hurts the web. It ends up being Google'…
Off 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.
This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries from https://mozilla.github.io/standards-positions/ and https://webkit.org/standards-positions/ This is a good example of how the chromium monoculture hurts the web. It ends up being Google'…
I think the feature to compare could be made a little more obvious - I can see why they would default to Chrome (both the most popular browser & also the one that shows the starkest difference), but tbh I find the most interesting comparison being against macOS Safari - that list seems really surprising to me. This also would of course be even nicer if you could define any browser as the "target" (e.g. compare Chrome…
This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries from https://mozilla.github.io/standards-positions/ and https://webkit.org/standards-positions/ This is a good example of how the chromium monoculture hurts the web. It ends up being Google'…
I think it's normally "harebrained" like hare/rabbit but hair brain doesn't imply any greater intelligence for sure. I've said folks are "single threads" to indicate something similar in more nerdy settings.
Earlier quoted context omitted.
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.
The 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.
The 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.
1) When loading a file, nothing needs to be different from the already available upload functionality. The user picks the file to load.
2) When saving a new file, nothing needs to be different from the already available download functionality. The user picks the name and the place to save it.
Only after 1 or 2 have already happened can the page request to update the file. With the same name and location. In this case, the user gets a prompt that explains the risks and asks the them to confirm the update.
Earlier quoted context omitted.
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…
We already have a diverse ecosystem of platforms which are capable of using hardware components for various experiences - we call them "the OS". It comes with a security model, permission prompts and all kinds of bells and whistles (it's a mature platform, developed for decades). The browser (agent) is a native app designed to allow users to access and navigate web resources (we call them pages or documents). Pages c…