Interesting MS<>Google partnership on the design front. Wish they had redesigned `<select multiple>` though. That's one component that really feels stuck a million years in the past
<select multiple> is in desperate need of a redesign. I made multi.js (https://github.com/fabianlindfors/multi.js) to fix this but hopefully browsers will take the matter into their own hands.
The current OS permission models used by applications and drivers that interface with these peripherals are much less secure than those used by browsers.
I'd say the opposite is true. With more powerful browsers, you are making web applications more powerful and remove the need for a desktop app.
Web apps, if built correctly, are probably more secure than desktop apps. Especially considering that you completely remove the need for user updates, since the website is updated by the developers.
Plus, webbrowsers implement a proper permissions model unlike native apps, especially on Android, used to do.
The more features like this a browser has the less excuse manufacturers of connected devices have for relying on mobile apps.
We were moving too far into a world where anything connected required a mobile companion app that inherently has a lifespan because of how averse to legacy apps the mobile ecosystem is.
Meh, only NDEF NFC protocol is supported. A little bit too restrictive. There are so many devices out there that could be configured from an authorised website but many of them use a proprietary binary tag format.
Hope they open it up a bit in the future. Just like they did with webUSB and webBT.
A. It unrelated but all of Google’s blog posts are unreadable on my iPhone. The text doesn’t appear, I just see the title. Hope it’s just me and google did t actually real safari compatibility.
[+] [-] jve|6 years ago|reply
> This version of Chrome removes TLS 1.0 and TLS 1.1. TLS (Transport Layer Security) is the protocol which secures HTTPS.
[+] [-] Krasnol|6 years ago|reply
https://www.mozilla.org/en-US/firefox/74.0/releasenotes/
[+] [-] Florin_Andrei|6 years ago|reply
[+] [-] bogidon|6 years ago|reply
[+] [-] fabianlindfors|6 years ago|reply
[+] [-] stevenwliao|6 years ago|reply
https://webnfc.app/
[+] [-] codemysoul|6 years ago|reply
[+] [-] mister_hn|6 years ago|reply
That's fundamentally wrong and insecure
[+] [-] Sephr|6 years ago|reply
[+] [-] moooo99|6 years ago|reply
Web apps, if built correctly, are probably more secure than desktop apps. Especially considering that you completely remove the need for user updates, since the website is updated by the developers.
Plus, webbrowsers implement a proper permissions model unlike native apps, especially on Android, used to do.
[+] [-] konart|6 years ago|reply
I'm confident that soon enough there won't be such a devision as web app and mobile app anyway. That's why imo.
[+] [-] whywhywhywhy|6 years ago|reply
We were moving too far into a world where anything connected required a mobile companion app that inherently has a lifespan because of how averse to legacy apps the mobile ecosystem is.
[+] [-] tonyedgecombe|6 years ago|reply
Because Google delivers its services through web browsers.
[+] [-] cameronfraser|6 years ago|reply
[+] [-] gridlockd|6 years ago|reply
What's fundamentally insecure about it? The permission model of the browser is better than that of desktop operating systems.
You can argue that it's more opportunity for exploits, but then again many (if not most) exploits are found in processing and rendering text.
[+] [-] wayneftw|6 years ago|reply
That's the only update I'm watching out for because I'll have to switch to another browser at that point.
I was going to start using Edge everywhere but now probably Brave after reading this - https://www.zdnet.com/article/brave-deemed-most-private-brow...
[+] [-] dazhbog|6 years ago|reply
Hope they open it up a bit in the future. Just like they did with webUSB and webBT.
[+] [-] moonbug|6 years ago|reply
[+] [-] yalogin|6 years ago|reply
[+] [-] Elidrake24|6 years ago|reply