RT @ChromiumDev: 🧪 Start experimenting with a new way to access browser and device data with User-Agent Client Hints. Available in Chrome 8…
@mhartington Love how many of the UI best practices of https://t.co/LpoNYtqD5v this implements. Great work. ðŸ’
@wesbos @SaraSoueidan The marketing is great and they’ve definitely created a hype. Will I pay $99 for it to start fresh, tell everyone about my new email, and set up tons of backup emails again? Probably no. It’s a cool tech demo, though. For another
@html5test @voxpelli @firt They emphasized *in part* in the blog post, so yeah, fingerprinting was an argument in not implementing, but not the only one.
@rowan_m I could also page your manager and mention that some of their reportees reports spare cycles. But you wouldn’t want me to do that, would you? /me pets cat.
@rowan_m It’s like inbox: zeroyoutu.be/gFBLiHpkcOkAq
If you want to test-drive this yourself, here’s the new branch: https://t.co/gGkKaiwGSJ.
Sneak preview of the 💷â€â™€ï¸ Service Worker Detector extension (https://t.co/0L1fYfz5tZ) working in Safari Technology Preview 109.
(Thanks, @xeenon, for the handholding in getting this up and running). https://t.co/eg3sLkldTq
@campuscodi @ZDNet The article lacks the source. This is the missing link for where you write “Apple said”: https://t.co/mBwQwiGFTG.
@xeenon 🎉 Thank you so much for the help! Greatly appreciated! It all worked fine nopic.twitter.com/rqgFvQb2NC2NC
@xeenon It’s probably the same thing with the missing references. I need to recreate the project. Be right back.
@xeenon Just did. The ID is FB7822308.
@xeenon Ah, I see. That’s the kind of thing I meant. Xcode n00b here, sorry. Let me try to fix my project then.
@xeenon Another small thing I ran into: inspecting a popup window only works if you set Web Inspector to open in a new separate window. It shows a white screen when run docked.
@xeenon Race condition :-) Just sent you this: https://t.co/qphUOCB0Bv https://t.co/HmmN6dgMKI
@xeenon This is from my `popup.html` file, note the highlighted parts. pic.twitter.com/Q0HKPGhlEQ
@xeenon Awesome, this was it. It seems there’re some issues with resolving relative paths. If I load everything from `/` it works. pic.twitter.com/RGCTpX1ebj
@xeenon Woohoo, managed to build an extension by creating a fresh extension via the wizard and then replacing the Resources.
Now I get `[Error] Failed to load resource: The operation couldn’t be completed. (Cocoa error -1000.)` in my popup.js. How do I
@xeenon I’ll give it a try as soon as I can. Unfortunately can’t install a beta build myself on my corp. MacBook.
@xeenon My suggestion would be to have the documentation be cross-read by someone who never touched Xcode and any of the App Store publication process.
@xeenon Thanks for the clarification. As many developers, I won’t start from scratch, but try to convert an existing extension. But good to know starting fresh is supported now on Catalina.
FWIW, I hope not to run into native issues like with the old Ed
🗣 PSA: If you want to play with Safari Web extensions (https://t.co/YpRKOOae2N), you need(!) to be on macOS Big Sur. I tried installing Xcode 12 beta on Catalina, switched to it, installed STP 109, and it still wouldn’t work. Confirmed by @xeenon: http
@nomsternom @webkit @ChromiumDev Agreed. What comes to mind are things like https://t.co/MjYX8pmHNY and https://t.co/eyQS25SMGc.
@nomsternom @webkit @ChromiumDev Yes, prompting isn’t the universal answer. I still think a mix of granting _some_ permissions on install and ad-hoc _grouped_ prompting for others could work, all while “forgetting†granted permissions after a certai
“They [@npmjs] realized it after the fact [of firing five engineers] that they let all the black people goâ€.—@nomadtechie
I don’t have details, follow Amal instead. â¤µï¸ https://t.co/pWkaLmRWJO