Hi all Giving myself a nice learning curve, I have developed some test with selectors. Each test is still under review and slowly becoming more complex. I can see some test pages splintering on to other test pages.
I am developing it in a way that it shows firstly if a browser doesn't supports a selector and then if a browser does support a selector it will show either a match or non match. Also the tests show if the CSS is filtering or targeting any browser due to non support or buggy support of a selector. I was surprised to find how many there were. I will also have to redo the test in html4.01 strict and xml. I have tested on Windows XP in FF 2.0.0.8, Mozilla 1.7.13, Flock 1.0.1, Opera 9.10, Opera 9.24, Safari 3.0.4 (beta) and IE7. I would like any feedback for any of the test with Mac browsers or some others browsers that I haven't got. I would also welcome criticism or suggestions about the techniques for showing non support and filtering or targeting of browsers. This I still have a lot of work with. The first test show my attempts with namespace. <http://css-class.com/test/css/selectors/namespace1.htm> <http://css-class.com/test/css/selectors/namespace2.htm> Each of these tests shows a lexical error with this |p.test3 when I try to validate the CSS. Why is this the only p.class showing the error? I not even sure if there should be the word namespace in the url string in the later test page as both test pages with or without the word namespace works. I sure someone will clarify my errors. The next test are with the Negation pseudo-class Selectors <http://css-class.com/test/css/selectors/negation.htm> The test on this page will needs to be done over several pages as I find that the test show quite broken support across browser land. Firefox and older Gecko is very broken and somewhat Safari but for different selectors. The next test are with Attribute selectors. <http://css-class.com/test/css/selectors/attribute.htm> This the only test that IE7 get a look in and surprisingly it passes with almost flying colours. It shows the way to target Safari at least on windows, which I believed is the same for Mac with case insensitivity. Some of the test seem to be repeated over and over but this is done to demonstrates all possible way that class names can be used either in the string in the html or CSS. The next test are with Attribute selectors with the Negation pseudo-class. <http://css-class.com/test/css/selectors/not-attribute.htm> This is almost the total reverse of the last page (used the last page as a base) and will have to be streamlined. This page fails at this time because IE7 seems to be picking up some of the colours which it should not since it does not support the negation pseudo-class. The browser support overall is in this order. Safari (beta) {Webkit) Firefox (newer Gecko) Mozilla (old Gecko) Opera IE7 The tests are intended to be used to check browser support or buggy support for various selector, not as a way to feed alternative styles to "x" browser. But having said that, I have done some extra test showing the possibilities. Kind regards, Alan <http://css-class.com/> ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
