browser-compat-data VS postman-app-support

> a lot of the data on the site actually comes from MDN

Eh... not really.

The feature support matrix (as linked on CanIUse) comes from the browser-compat-data repo. Here's the HTML element's source data: https://github.com/mdn/browser-compat-data/blob/main/html/el...

This doesn't contain the testing and usage info that CanIUse cites for support, though, just which browser versions included which features.

CanIUse also points to their own repo, which contains a lot of data: https://github.com/fyrd/caniuse

But I can't find an easy entry point to find where they're getting the numbers for a specific element. The data on there seems to be primarily for features.

So the more precise question is, where is CanIUse getting HTML element testing and usage numbers from? Because that seems to be the issue.

The key factor for web development to stop new CSS features is cross-platform compatibility. If you want to know the compatibility data of a new feature, you can get it through platforms such as Can I Use , Browser Compat Data and Time to Stable .

Yes, Mozzila’s browser-compat-data (https://github.com/mdn/browser-compat-data) is the authoritative source.

Just noting that the browser support matrix is right here: https://web.dev/patterns/advanced-apps/contacts/#:~:text=con...

It's an Eleventy widget powered by MDN's browser-compat-data: https://github.com/mdn/browser-compat-data.

https://developer.mozilla.org Is your best friend, they even have an examples how to use it

Visit any website on https://developer.chrome.com, https://developer.mozilla.org or https://docs.microsoft.com.

W3Schools and MDN Web Docs are two great resources to learn about elements and all about HTML and CSS. Kevin Powell has a great YouTube channel which explains everything you search for. If you want to incline in your HTML and CSS skills pretty quickly, think of your objective, maybe even sketch it out, then search absolutely everything on Google and it will give you the answer. If not, this subreddit is always open. Bon voyage

Do you have any details on the equivalent Postman change? How long ago did Postman force users to create an account? I found this github issue, but I'm not sure if it's what everyone keeps referencing.

https://github.com/postmanlabs/postman-app-support/issues/12...

Possibly user agent add it to postman https://github.com/postmanlabs/postman-app-support/issues/3827

As you can see, this solution worked as expected, but it still has a big concern. The idea of using user email and checking their permission will not prevent malicious people from using an admin email, which can be easy to get with social engineering, and use programs like Insominia or Postman to get the same response as an unprotected endpoint.

You have installed Postman.

Learned about curl https://curl.se/ and played around with postman https://www.postman.com/ some more.

Postman installed

The JWT authorizer is ready to use! We can use Postman or curl to test the endpoint and the authorizer.