2 more tests submitted from gtalbot.org

[Gérard Talbot-2]

Hello all,

2 more tests to the CSS 2.1 test suite:

Margin collapsing, test 1 and 2

All the tests are available (in HTML 4 and XHTML 1.1), downloadable,
reviewable from

http://www.gtalbot.org/BrowserBugsSection/css21testsuite/

Filenames of tests will have to be reviewed...

regards, Gérard

[Gabriele Romanato]

You can make these tests on font properties interactive/dynamic by displaying the word 'passed' only when the style is actually computed by using getComputedStyle() or alternatively, the css() method of the jQuery library. this suite actually needs more interactive tests.

bye, ^.^

Gabriele

http://www.css-zibaldone.com/
http://www.css-zibaldone.com/test/ (English)
http://www.css-zibaldone.com/articles/ (English)
http://dev.css-zibaldone.com/  (English)

[L. David Baron]

On Wednesday 2009-08-19 10:31 +0200, Gabriele Romanato wrote:
> You can make these tests on font properties interactive/dynamic by
> displaying the word 'passed' only when the style is actually computed by
> using getComputedStyle() or alternatively, the css() method of the jQuery
> library. this suite actually needs more interactive tests.

Why does it need more interactive tests?  I'd rather it have simple
tests that can be tested as automatically as possible.

Also, I wouldn't want tests to use jQuery; that brings in a lot of
code, which makes the test much more complicated and potentially
harder to debug, and it also introduces browser-specific code into a
test suite, which we don't want.

-David

--
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/

[Gérard Talbot-2]

Hello Gabriele,

> You can make these tests on font properties interactive/dynamic by
> displaying the word 'passed' only when the style is actually computed by
> using getComputedStyle() or alternatively, the css() method of the jQuery
> library.

Well, I wish tests would remain as simple and reduced as possible. Formal,
clear too. For browser manufacturers, this is best too.
I am using "Nth test passed" in
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/t1503-font-family-01.html

One interesting unique aspect of the test
http://www.gtalbot.org/BrowserBugsSection/css21testsuite/t1508-font-11.html
is that, despite not supporting font system reserved names
https://bugs.kde.org/show_bug.cgi?id=197544
, Konqueror 4.2.4 is able to pass t1508-font-11.html test. The font-size
is properly, correctly parsed and rendered: no red viewable.

> this suite actually needs more interactive tests.

Can you elaborate more on what you may be seeing or meaning with
interactive tests?
I may agree with you. If such interactive tests are tutorial-like and can
be useful for conveying how properties work, then IMHO they could be
included in the CSS 2.1 test suite, otherwise they should be available
from inside the CSS 2.1 spec itself. Interactive demo can help understand
how CSS properties work or interact with each others.. What I have in mind
here is some kind of test like this:

http://www.gtalbot.org/BrowserBugsSection/MSIE7Bugs/Float2p-with-clear-left.html
(not perfect, not ideal... but just giving a general idea here)

Every single code examples given in CSS 2.1 spec. should be available
somewhere, testable in a webpage, for ordinary, human web authors... A
spec can be a very dry thing to read; an interactive well-designed demo,
webpage-test-example may be something that one can bookmark and remember
for a long time... Same thing with a schematic picture explaining, showing
respective concepts (eg: the CSS box model) and how they relate to each
other.
E.g.:
http://www.gtalbot.org/BugzillaSection/DocumentAllDHTMLproperties.html

Unless I'm wrong, there are only 3 typical properties naturally involving
user interaction in CSS 2.1, which would require interactivity: :hover,
:focus and :active

best web-standards-regards, Gérard Talbot