An open source initiative to increase cross-browser compatibility. Report bugs from anywhere on the web.
In between broken stars
Joined December 2013
- Tweets640
- Following29
- Followers1.3K
- Likes330
webcompat.com retweeted
Interop 2022 showed significant improvements in the interoperability of multiple platform features.
We’re thrilled to announce the launch of Interop 2023, a cross-browser collaboration to improve web interoperability! 🎉🎉
hacks.mozilla.org/2023/02/an…
webcompat.com retweeted
The state of CSS survey just started!
Answer CSS questions here:
survey.devographics.com/surv…
The survey results will be public and help browser vendors prioritize their roadmaps and work towards better compatibility between browsers.
webcompat.com retweeted
Today @Apple, @Bocoup, @Google, @Igalia, @Microsoft and @Mozilla are announcing Interop 2022.
We have collaborated with the other major browsers and standards bodies on identifying the key technologies needed to fully experience the web. hacks.mozilla.org/2022/03/in…
webcompat.com retweeted
Week of 08-Mar-2022
It's in the docs
docs.microsoft.com/en-us/dep… – at Berlin, Germany
webcompat.com retweeted
Version 100 in Chrome and Firefox hacks.mozilla.org/2022/02/ve…
And Edge 👋🏼 @mozhacks
webcompat.com retweeted
This was a massive undertaking, a whole new tool to automate compat data collection, and thousands of PRs. I’m happy to have been on this journey with @queengooborg!
This Post is from an account that no longer exists. Learn more
webcompat.com retweeted
Blink: Intent to Deprecate and Remove: Event.path groups.google.com/a/chromium…
webcompat.com retweeted
To followup, this issue is known and will be fixed in our next EDC release (ETA next week, or shortly after)
webcompat.com retweeted
A good opportunity, for anybody, to tell us at the W3C Audio Working Group, of what they need / want / like / dislike about anything related to audio on the Web. It's not a particularly long survey, and the answers will certainly help with prioritization.
webcompat.com retweeted
Some ideas and contexts around auto-discovering #webcompat issues and a bit of history on some projects. How do you know that there is a webcompat issue? otsukare.info/2021/10/26/web…
webcompat.com retweeted
📝 How to win at CORS! Not just how CORS works, but also the history and reasons behind it.
Includes the hot new app everyone's talking about: The CORS playground!
jakearchibald.com/2021/cors/
webcompat.com retweeted
Web developers, have you recently run into a browser compatibility but don't know where to file a bug? Please file an issue at github.com/webcompat/browser… and I will take a look together with friends at Mozilla. This is an experiment to see if this approach works well. #browsercompat
webcompat.com retweeted
[CSS Cascade Layers] Enable by default
bugs.webkit.org/show_bug.cgi… (probably in the next Safari Technology Preview and regular Safari in spring 2022)
With progress in Chromium bugs.chromium.org/p/chromium… and Firefox bugzilla.mozilla.org/show_bu…, could this be available everywhere in 2022?
webcompat.com retweeted
The Mozilla Webcompat team will be soon looking for any issues with Firefox/100. @cpeterso has worked on a Firefox experiment to send the Firefox/100 UA to nightly users. And @denschub tested the JS libraries and so far so good (for the future).
otsukare.info/2021/04/20/ua-…
webcompat.com retweeted
I've been trying to work out if Chrome 100 will break UA checks in ways similar to the legend that Windows 9 was skipped because developers checked for 9 in the version to avoid checking for 95 or 98...
paul.kinlan.me/chrome-100/
Let me know if you might get hit by this.
webcompat.com retweeted
Please report them through the @webcompat website, they do a lot of work to get these things fixed. :)
webcompat.com retweeted
#Webcompat has always had a very strong community participating on reporting bugs, doing awesome outreach work to the broken websites owners, improving the Web for all.
All our thoughts go these wonderful contributors in these difficult times. #India #COVID19
webcompat.com retweeted
#tinyCSStip
Careful with % round values for inset()!
👉 Chrome takes them to be relative to original element rectangle (screen #2)
while
👉 Firefox takes them to be relative to the rectangle obtained after clipping (screen #3)
Live test on @CodePen codepen.io/thebabydino/pen/v…
ALT Code screenshot: div { width: 90vh; height: 90vh; background: deeppink; clip-path: inset(80% 0 0 round 8%) }
ALT Screenshot of result in Chrome: %-valued rounded corners of rectangle resulting after the clip are relative to the original element rectangle.
ALT Screenshot of result in Firefox: %-valued rounded corners of rectangle resulting after the clip are relative to the this very rectangle obtained after clipping.
webcompat.com retweeted
Karl Dubost: Working With A Remote Distributed Team (Mozilla Edition) ift.tt/3eFPPyF
