css3test icon indicating copy to clipboard operation
css3test copied to clipboard

Published 20 hours ago • verified publisher icon LeaVerou

Browser Comparison

Open brettpostin opened this issue 10 years ago • 8 comments

As the CSS3Test seems to be the most comprehensive online test available, it would be good to have the ability to compare your results with other browsers, much like on HTML5Test.

I've been searching everywhere for some sort of summary of the collected data on Browserscope but without much luck.

Also there seems to be quite a lot of data on Browserscope, however I'm unable to find any way to download/analyse this data myself, and much of it seems to conflict with one another. Is there any way to actually do this?

brettpostin avatar Oct 31 '13 07:10 brettpostin

If you want to know If a property is supported, you can always use www.caniuse.com

miguelfrias avatar Oct 31 '13 07:10 miguelfrias

I'm aware of that I'm just looking for a quick overall comparison between browsers (like in HTML5Test).

brettpostin avatar Oct 31 '13 13:10 brettpostin

@LeaVerou is it possible to set up a database for CSS3Test as a first step for this?

Then it would probably be easier for others to help implementing this.

SebastianZ avatar Jul 15 '14 08:07 SebastianZ

Here are the main requirements to allow comparison between browsers:

  • [ ] Implement a way to output the data as structured info (probably covered by #106)
  • [ ] Set up a database structure to store the results referring to a specific browser version
  • [ ] Add browser data (at least all main current versions)
  • [ ] Add a frontend that allows users to compare the results

Sebastian

SebastianZ avatar Aug 14 '19 20:08 SebastianZ

That's basically what BrowserScope is for, except the Results link has been broken for years, I think because we have too many features. I wonder if we could fix it, and whether it would be sufficient if so. If not, is there an alternative to BrowserScope these days? If not, I guess we could set up a Firebase database and use that.

LeaVerou avatar Aug 19 '19 14:08 LeaVerou

I've filed #218 to come up with a way to save the results.

Regarding a basic version of this feature, I could imagine to get away without a real DB. Instead, we could create a JSON structure containing info about the support for the different features in different browsers. Or we might use the data from https://github.com/mdn/browser-compat-data.

I'd still prefer some kind of real DB but for a first version I think we won't need it.

Sebastian

SebastianZ avatar Jan 07 '22 23:01 SebastianZ

I've filed #218 to come up with a way to save the results.

Regarding a basic version of this feature, I could imagine to get away without a real DB. Instead, we could create a JSON structure containing info about the support for the different features in different browsers. Or we might use the data from mdn/browser-compat-data.

I'd still prefer some kind of real DB but for a first version I think we won't need it.

Sebastian

How would we store data to it? Manually?

Firebase has a pretty nice entirely client-side API, we could it there automatically, then the more people that visit css3test, the more data we have.

LeaVerou avatar Jan 08 '22 11:01 LeaVerou

How would we store data to it? Manually?

The strategy is to run the tests on different browser versions using BrowserStack, export the data from there and merge it into a big JSON file. This will probably need a way to export the results as discussed in #106. While a lot can be automated, I expect that process to still require a lot of work.

Firebase has a pretty nice entirely client-side API, we could it there automatically, then the more people that visit css3test, the more data we have.

I have no experience with Firebase. If you have used it and believe it's a good choice for this use case, I'm all for it.

Sebastian

SebastianZ avatar Jan 08 '22 22:01 SebastianZ