@nill It seems like this affects only the iframe embed. I have opened https://t.co/xzTC9vwJz6 that prunes the `allow` values to just the needed ones, since the browser was complaining about an unknown value of `”vr”`. Let’s see if this fixes the issue onc
RT @MozDevNet: As of November 2, 2020, The Yari beta is open. 🎉ðŸ¤
Find out how you can get involved, what kind of feedback we’re looking fo…
@TheRealNooshu @AndyDavies @tomtaylor Thanks a lot! Same reaction as in https://t.co/xFPHhraonB.
@AndyDavies @tomtaylor @TheRealNooshu Oh, wow. That’s a surprisingly small share. Thanks for, well, sharing!
@argyleink Firefox should be easy, it’s Safari that requires special treatment. I still roll each update submission manually. Not ideal, but workable for now. Would love to learn about best practices in that area.
@argyleink I’m trying to deal with the different builds of my Chrome/Firefox/Safari extensions in separate branches, too (like your Firefox branch: https://t.co/fasN1rhFf3). I’m not sure if that’s the best way. uBlock Origin has a different system (
The `local()` function for CSS font face declarations (https://t.co/atbJ97B9RN) will soon be disabled ⤵ï¸.
For actual local fonts access, consider giving the Local Font Access API a try: https://t.co/084565DaOW. https://t.co/HLFizzKrpf