|Summary:||[METABUG] Get a perfect score on css3test.com|
|Product:||WebKit||Reporter:||Trevor Downs <cyberskull>|
|Severity:||Normal||CC:||bfulgham, code.vineet, eric, gyuyoung.kim, hyatt, kennyluck, menard, sebastianzartner, shanestephens, simon.fraser, syoichi, webkit-bug-importer|
|Version:||528+ (Nightly build)|
|Bug Depends on:||27576, 37514, 83885, 84426, 86703, 87673, 88328, 103597|
Description Trevor Downs 2012-02-20 21:24:10 PST
The website <http://css3test.com/> tests browsers for the existence of CSS3 features and can be used to gauge the progress of features. I'd like to see WebKit hit 100% before the other engines do. Note that this site only currently checks for the existence of features, not that they are correct. * Safari 5.0.6 on 10.5.8 PPC: 57%, determined by passing 386 tests out of 783 total for 187 features.
Comment 1 Simon Fraser (smfr) 2012-02-21 09:55:55 PST
I think it's more useful to focus on the missing properties one at a time.
Comment 2 Trevor Downs 2012-02-21 18:44:49 PST
(In reply to comment #1) > I think it's more useful to focus on the missing properties one at a time. Then create a bug for the missing feature! :)
Comment 3 Shane Stephens 2012-02-22 20:03:55 PST
Please do file bugs on individual properties or failures, and link them back to this bug via the "Blocks" field. Please don't expect others to necessarily contribute to this :) If there are no bugs that this bug depends on in a couple of weeks I'll be inclined to close it due to lack of interest.
Comment 4 Eric Seidel (no email) 2012-04-13 16:10:29 PDT
Interesting. I enjoyed working on html5test... but have been sad that the author hasn't responded to any of my email/bug feedback on the tests. Perhaps I'll look at this one after I finish <iframe seamless>.
Comment 6 Sebastian Zartner 2023-05-02 12:37:55 PDT
> I'd like to see WebKit hit 100% before the other engines do. This probably won't ever happen. css3test.com is constantly updated by me and others to cover all features defined in the CSS specifications, including experimental ones. So as long as there are features added to CSS and that site is being maintained, no browser will ever reach 100% coverage. Therefore, and given the fact that this bug didn't get updated for more than 11 years and all blocking bugs got fixed in the meantime, I vote for closing this bug. Sebastian