As a user, sharing links, and especially being sure you are sharing the right link to deliver a seamless experience to whoever youre sharing it to is getting increasingly difficult. With content wrapped in various elements, inconsistent context menus and other pain points. Not to mention simply sharing the url from the bar can take 5-7 clicks for a user to feel comfortable they have the entirety of the url, copied, then pasted it. Not to mention all the junk syntax associated with a particular users instance, which makes for ugly links. Something the web was once fundamentally good at, has become a hassle. All of this goes doubly so for mobile web browsers
More and more Layered APIs in the future will definitely help developers ship less code. Maybe with an acceptable compromise of making the browser heavy. But nonetheless, a virtual-list component is going to be a life saver.
As a user, sharing links, and especially being sure you are sharing the right link to deliver a seamless experience to whoever youre sharing it to is getting increasingly difficult. With content wrapped in various elements, inconsistent context menus and other pain points. Not to mention simply sharing the url from the bar can take 5-7 clicks for a user to feel comfortable they have the entirety of the url, copied, then pasted it. Not to mention all the junk syntax associated with a particular users instance, which makes for ugly links. Something the web was once fundamentally good at, has become a hassle. All of this goes doubly so for mobile web browsers
The biggest issue I can think of at first hand is that you can bypass the origin monetization and get the content without approval.
More and more Layered APIs in the future will definitely help developers ship less code. Maybe with an acceptable compromise of making the browser heavy. But nonetheless, a virtual-list component is going to be a life saver.
One question, can policies be applied to the body or HTML tag or is it only for IFrames?
The plan is to allow you to opt in to policies on your main page via HTTP Headers, much like CSP.
It can be applied to your own document via an HTTP Header only at the moment: wicg.github.io/feature-policy/#feature-policy-http-header-field
How about Proper Tail Calls for a platform performance enhancement?
is the "experimental productive feature flag" can be turned on `chrome://flags/` ?? but I can't find it.
I am using chrome 66
you type chrome://flags to the search bar
Found it! It's available under dev and/or canary.
I think he said you need beta or canary.
found them in chrome canary, thanks !
Bam! Didn't know that XHR was synchronous. I always thought that was async.
It has both modes. Sync was deprecated a long time ago.
So now it is only async?
how to handle sync calls then? I need my data from a service before getting into next async lets say.
download333 sweet. Thanks!
XHR.open('GET', url, true/false)
true = async
flase = sync
Akash Potdar You should probably use async/await, promises, server-side data aggregation or event listeners instead of sync fetches
Can somebody make Google + better?
.
Web packaging + IPFS. 😳
7