Chrome 78 Beta: a new Houdini API, native file system access and more
41–50 of 80 posts
Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#42Earlier quoted context omitted.
If would be interesting if you could allow a site to "open as application" (instead of open in new tab) - or this could even be called "install". The site would then appear in your OS like any other app, and may or may not have some of the browser chrome (URL bar, tabs, navigation buttons) depending on the site. I currently have many pinned tabs - email, music - where I'd happily promote them to "apps". Even some of…
Sounds like you’re describing the Progressive Web App (PWA) install that Chrome recently added. Coming to Firefox (if not there already), and Edge. Not holding my breath for Safari though.
EDIT: This post [1] says background switching should be working in iOS 13.
[1] https://medium.com/@firt/iphone-11-ipados-and-ios-13-for-pwa...
Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#43Browsers need a bright line between documents (HTML and CSS) and applications (electron-like, notifications, complex APIs, access to features that affect the user's security). Plain HTML documents are SEO friendly, are a11y friendly almost by default, back/forward navigation works, and HTML doesn't chew battery and bandwidth on JavaScript. For our web app the biggest pain points are: security (hard to integrate third…
> Unfortunately Google don't seem to want to encourage plain HTML documents (instead the insane AMP shit). AMP is just plain HTML documents [0]. The only difference between an amp page and a standard HTML page are the following: 1. It includes the amp javascript library: ` `" rel="nofollow">https://cdn.ampproject.org/v0.js"> ` 2. It contains amp within: ` ` 3. It must contain: ` `, has a ` `, a ` ` and specify ` `. 4…
2. AMP is a set of web components that rely on JS to properly render.
3. If JS is disabled, page content is hidden by a CSS declaration
4. AMP pages are treated differently by the dominant search player
So yes. On the surface it’s “just plain HTML page”. Technically.
Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#44Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#45Earlier quoted context omitted.
A lot of them just need to be on the taskbar/notification area and not in a browser tab, honestly.
If would be interesting if you could allow a site to "open as application" (instead of open in new tab) - or this could even be called "install". The site would then appear in your OS like any other app, and may or may not have some of the browser chrome (URL bar, tabs, navigation buttons) depending on the site. I currently have many pinned tabs - email, music - where I'd happily promote them to "apps". Even some of…
Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#46Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#47Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#48Earlier quoted context omitted.
> The "coherence and familiarity" argument for native apps is only half the story though. The user only uses the application in the platforms that one uses; so cross-platform coherence is mostly meaningless. > And as an app developer, when you have to make a decision regarding whether you should be familiar and coherent to the rest of the operating system or the other installs of your app, that's pretty much always g…
The user only uses the application in the platforms that one uses Most people only use one desktop and one mobile OS, but it's extremely common to use the same app on both desktop and mobile. If your Mac and Windows apps both have to be consistent with your iOS app, they end up having to be consistent with each other.
If the Mac version and Windows version of the app can be consistent with the mobile version(which will have different interfaces), why can’t they be consistent with each other(between the two desktop apps) while having different interfaces?
Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#49Earlier quoted context omitted.
A lot of them just need to be on the taskbar/notification area and not in a browser tab, honestly.
If would be interesting if you could allow a site to "open as application" (instead of open in new tab) - or this could even be called "install". The site would then appear in your OS like any other app, and may or may not have some of the browser chrome (URL bar, tabs, navigation buttons) depending on the site. I currently have many pinned tabs - email, music - where I'd happily promote them to "apps". Even some of…
Open the page you want to be an "app", and on the Chrome three-dot menu, select More Tools / Create Shortcut...
Edit the name as you wish and check the "Open as window" checkbox, then click OK.
Now you have a shortcut on your Start menu that works like any other app shortcut. You can pin it to the taskbar, save it to the desktop, any of the usual things. And when you open the app it will have its own window and its own icon on the taskbar.
This works on Windows and Linux at least - have not tried it on macOS.
Re: Chrome 78 Beta: a new Houdini API, native file system access and more
#50For those that are interested in the security around file system access please go here: https://developers.google.com/web/updates/2019/08/native-fil... If you look at the various restrictions, you will see that the user is in control of most of the operations. It restricts access to system folders. I do think that many lay people may still fall prey to attack vector sites that may save an evil EXE or something, hopin…
The mitigations appear around overriding Files in user and system directories and revoking access.