We do have a great tool such as CanIUse and of course, BaseLine is not going to replace it. - Source: dev.to / about 2 months ago

Lots of parts to WebRTC ( https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API ) but none that I know that can knock out something outside of your browser. It could maybe overload RAM and get killed. Try using the offending website on a browser/OS that _doesn't_ have WebRTC such as https://caniuse.com/?search=webrtc. Or try with WebRTC disabled. Possible you're getting throttled by your router or ISP when... - Source: Hacker News / 17 days ago

A11ySupport.io: The caniuse of accessibility. Lists compatibility of various browser accessibility features for different screen reader and browser combinations. - Source: dev.to / 29 days ago

Ah yep! I just didn't wait long enough. Very cool. Seems like it took a lot of work. And it seems better than other browser-based video editors I've seen in the past, so kudos. TIL about the webcodecs API to get frames of video and chunks of audio: https://caniuse.com/?search=webcodecs. - Source: Hacker News / about 1 month ago

Can I X, is a question about the readiness/compliance of a certain thing at time = now. Can I use CSS version X was the iconic early meme. https://caniuse.com/?search=css3 For a generalized example, if you wanted to know if the basketball courts were ready for you to “ball it up” in a certain city, it’d be caniball.com If you want to know if you can use a certain frontend technology, the idea is like: canwefigma?... - Source: Hacker News / about 1 month ago

Https://shadow.goose.icu/?http://acid3.acidtests.org/. - Source: Hacker News / 8 months ago

During the browser wars, web developers created “Acid Tests” to see how well a browser supported various style sheet and markup conventions. When the acid tests became popular, there were accusations that browser engineers were manipulating their rendering engines to pass those tests. For instance, some cascading style sheet attribute would pass the test, but fail to work as expected under normal use on a web page. Source: about 1 year ago

I am sure that both firefox and chromium-based browsers will pass most of something like ACID3 test. But at this stage standards have nothing to do with reality. Standards define perhaps 10% of the code you are writing and interpretation of the rest 90% of the code is up to the browsers. Source: almost 2 years ago

The old version (http://acid3.acidtests.org/) will reach 97/100 on modern compliant browsers. There is a newer version (https://wpt.live/acid/acid3/test.html) which incorporates the changes made to the specs in the meantime, so modern browsers will reach 100/100 on this one again. The test was carried out against this version, as you can see in the address bar in the screenshot. - Source: Hacker News / about 2 years ago

Different PRESENTATION of content on mobile is good. Different content on mobile is the definition of r/assholedesign. It does not matter if the http user agent is a "good" one or not, it should just work. There is a specification, numerous accessibility guidelines, plenty of tests and benchmarks. This isn't 1999 anymore... 🤷‍♂️. Source: over 2 years ago