Looks like the perfect place to fake some browser chrome and trick people...
https://www.theregister.com/2017/01/19/browser_line_of_death...
Closing a 30 pixel gap between native and web
11–20 of 313 posts
Re: Closing a 30 pixel gap between native and web
#12I think this is a sign that Microsoft sees the writing on the wall. There will be a day when Windows is left behind, and they want to make sure that they can continue to deliver the Microsoft experience, even on other platforms.
Re: Closing a 30 pixel gap between native and web
#13Looks like the perfect place to fake some browser chrome and trick people... https://www.theregister.com/2017/01/19/browser_line_of_death...
I think you'll only get access to this API if the user has explicitly installed your app as a PWA, not just when visiting it as a webpage.
Re: Closing a 30 pixel gap between native and web
#14Oh look they turned Chromium into IE6. Forced ads, difficult to eviscerate search engines, proprietary extensions, dubious security posture! Oh goody!
Re: Closing a 30 pixel gap between native and web
#15With all this Electron and PWA focused development a cannot shake a feeling that we add an extra layer of a "runtime" on top of an operating system, that could be avoided. An extra layer which occupies RAM space and processor time which feels unnecessary but it is where we are headed. I wonder if the reason is simple, that we (myself included) have not provided anything better or the reason is that big corporations w…
This.
I encountered hell the other day. I saw a corporate Citrix deployment that had 45 users running three electron apps on an underprovisioned server with the CPU, disk and memory rammed at 100% lagging out. That’s 135 separate browser stacks basically.
Microsoft are moving office to this stack as well. Ugh.
Of course I was there trying to work out why our simple old fashioned web app was running slowly in a chrome tab…
Re: Closing a 30 pixel gap between native and web
#16Looks like the perfect place to fake some browser chrome and trick people... https://www.theregister.com/2017/01/19/browser_line_of_death...
I think you'll only get access to this API if the user has explicitly installed your app as a PWA, not just when visiting it as a webpage.
And then a shady company offers to buy the owner's website...
Re: Closing a 30 pixel gap between native and web
#17Looks like the perfect place to fake some browser chrome and trick people... https://www.theregister.com/2017/01/19/browser_line_of_death...
That was my first thought as well, but I couldn't remember the name for that boundary. I hope there is a well-designed per-site control/setting/user consent system to keep tech support scam sites (or worse!) from adding one more tool to their arsenal.
Re: Closing a 30 pixel gap between native and web
#18I think this is a sign that Microsoft sees the writing on the wall. There will be a day when Windows is left behind, and they want to make sure that they can continue to deliver the Microsoft experience, even on other platforms.
I don’t think Windows is ever going to be left behind, you still need a kernel to make use of all your hardware and an OS to give users something to do. I view this move as Microsoft recognizing that the future of most development is cross-platform web technologies and they need to give Windows users reasons not to migrate to macOS and ChromeOS (though it’s ok if they do as long as they’re paying for O365 and Azure).
Re: Closing a 30 pixel gap between native and web
#19> ability to create their own title bar experiences
It was a sad day, IMHO, in UX-world when this became possible in desktop apps. The window system should own the chrome and the apps should not be able to touch it.
Re: Closing a 30 pixel gap between native and web
#20Earlier quoted context omitted.
I think you'll only get access to this API if the user has explicitly installed your app as a PWA, not just when visiting it as a webpage.
And then a shady company offers to buy the owner's website...
That’s a real problem, of course, but it seems fairly equivalent to any native app you install that can update itself or otherwise make a network request to obtain instructions.