@AnaestheticsApp @Adobe @Photoshop Thank you :-) I don’t even pretend to be a Wasm expert, I was mostly just glad that my samples compiled successfully…
@mthie @Adobe @Photoshop Thank you very much! I learned a lot, too, when I did the research for this talk. 😅
🙀 Missed the @ChromiumDev team group photo opportunity yesterday in Google I/O Adventure. Thanks to Photoshop on the Web, it was an easy fix, though… twitter.com/tomayac/status…L#GoogleIOI#IO222pic.twitter.com/tV5VdXsRtrtr
jaffathecake The web technologies Adobe used to bring Photoshop to the web:
➡️ Advanced web assembly, like threads and SIMD.
➡️ The filesystem API.
➡️ P3 colour space.
➡️ Web components via lit.
➡️ Service workers.
Great talk by @tomayac! #GoogleIO youtu.be/CF5zZZy0R9U
@LinkofHyrule89 @Adobe @Photoshop 🧢 Haha, I guess the video crew would hate it if they needed to get the lights right if I wore the hat for filming.
chriscoyier I was fiddling with the iframe security attributes on CodePen this week and wanted to write up just what a confusing situation all that is.
blog.codepen.io/2022/05/11/ifr…
@chriscoyier The `allow` value is a serialized permissions policy (w3c.github.io/webappsec-perm…) whereas the `sandbox` value is an unordered set of unique space-separated tokens (html.spec.whatwg.org/multipage/comm…). So one is “complex”, the other “simple”.
@chriscoyier The `allowpaymentrequest` attribute was removed (github.com/w3c/webappsec-…), and `allowfullscreen` must have no effect if `fullscreen` appears in `allow` (w3c.github.io/webappsec-perm…).
hashseed Super proud of what the @ChromeDevTools team delivered! youtu.be/YqWEqYa-evk