The DevTools update is amazing: <a href="https://www.youtube.com/watch?v=uddZX9ZK6wY" rel="nofollow">https://www.youtube.com/watch?v=uddZX9ZK6wY</a><p>Break point like console logging is a neat idea.
SXG[0] looks promising - allows signing (and subsequently caching externally) whole HTTP exchanges.<p>This may be useful for improving security, especially of CDNs. Binary Transparency seems to be one of the use cases mentioned in the spec[1] - perhaps someday this would be used for an unified scheme for signing application packages/updates, without reinventing the wheel every time.<p>[0]: <a href="https://developers.google.com/web/updates/2019/03/nic73#sgx" rel="nofollow">https://developers.google.com/web/updates/2019/03/nic73#sgx</a><p>[1]: <a href="https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.appendix.A.4" rel="nofollow">https://wicg.github.io/webpackage/draft-yasskin-http-origin-...</a>
This is a huge release. Supporting PWA installation cross-platform provides a viable alternative to Electron-style bloat for many apps, and shipping SGX is useful for anyone who dislikes the AMP UX. Kudos to the Chrome team.
Somehow, the update to Chrome 73 managed to ruin Chrome Sync on my work Mac. I have to "unpause" sync every time I run Chrome and I'm logged out of every account after closing the app, although I do allow cookies and don't clear them on close. My passwords don't autofill anymore, either.<p>What's the point of buying into the whole Chrome Sync thing if it randomly dies for no apparent reason?
So, are these "Constructable Stylesheets" a non-standard Chrome-only web feature that Google designed and implemented, or what's going on here?
Regarding signed exchanges:<p>"When the browser loads this Signed Exchange, it can safely show your URL in the address bar because the signature in the exchange indicates the content originally came from your origin."<p>- the original website will not see these requests in its logs. Can visitors even tell that their browser is not accessing the server that shows up in the address bar? Their privacy is being violated.<p>- when the original website deletes or modifies a resource, the old outdated version may still be distributed by a 3rd party
Desktop PWA update looks promising and considering the last update, allowed many to upload PWAs on Google Play store. I feel the promises are finally coming true.
This update includes everything in V8 v7.3 as well: <a href="https://v8.dev/blog/v8-release-73" rel="nofollow">https://v8.dev/blog/v8-release-73</a>
Has anyone else noticed a reduction in New Tab icons? I used to have 10 defined, but now it will only show 8 of them. OSX 10.14.3, Chrome 73.0.3683.75.<p>It also seems to sometimes not want to display the text for the New Tab icons in white and picks a nearly-imperceptible slightly-darker grey.
I briefly looked around and it seems like desktop PWA are not yet supported by Firefox. At least I haven't found a way to add an app to the desktop like we can do in Chrome. A bit disappointing.
On macOS at least, opening a PWA .app also launches Chrome, and quitting Chrome also quits any PWAs you have open. That's not a stellar experience.
So Chrome supports dark theme, and PWAs can now be installed, but the PWA window does not support dark theme. Ironic. Two features developed in isolation?
Intel SGX[0] is a specific technology supported by the CPU for encrypting application memory. Is the acronym used differently in the context with Chrome?<p>[0] <a href="https://software.intel.com/en-us/sgx" rel="nofollow">https://software.intel.com/en-us/sgx</a>
We need less PWAs, not more. Many people are already confused enough when it comes to grasping the difference between websites and native applications. Another "standard" created to consolidate Google's position in the market.