Re: img_border_percent , object_border_perc and object_border_pixel testcases

> Hi GĂ©rard,
>

Hello Ms2ger,

Thank you for your reply.

> On 09/29/2011 08:36 PM, public-html-testsuite@gtalbot.org wrote:
>> http://w3c-test.org/html/tests/approved/xhtml5/img_border_percent.xhtml
>> http://w3c-test.org/html/tests/approved/xhtml5/object_border_perc.xhtml
>> http://w3c-test.org/html/tests/approved/xhtml5/object_border_pixel.xhtml
>  >
>> So, the logical question would be how far back should backward
>> compatibility go in HTML5?
>
> As specified in the Rendering section, in this case. See [1] in
> particular.
>
>> All those testcases have no link to their authors. Is that normal? I
>> mean,
>> submitted testcases do not have to indicate their author or sources?
>
> That's normal, yes.


I do not agree with such policy. There is enough anonymity on the web as
it is. People who want their testcases to be taken seriously should have
their real names mentioned and a way to reach them.


>> All those testcases have no assertion, no explanation for the rendering.
>> If border="50%" is to be parsed and have a rendering effect with a
>> border,
>> then shouldn't the testcase have an assertion defining and explaining
>> with
>> regards to which element (containing block or element itself?) is such
>> percentage applied on?
>
> The test asserts that "50%" is treated as "50", as required by [1].

In my opinion, the rules, process, method of parsing and rendering such
testcases should be indicated with an adequate <meta assert="" name="">
(added in the testcase) and adequate <link rel="help" href="" title="">
(added in the testcase) to link precisely to relevant section of the spec.
Especially if the expected result of such testcase is not so obvious or
intuitive or indicate a clear divergence with previous specification and
parsing.

The 7th step of such "rules for parsing non-negative integers" state
"
If the character indicated by position is not one of U+0030 DIGIT ZERO (0)
to U+0039 DIGIT NINE (9), then return an error.
"

If I understand this 7th step within the whole set of steps, then such 7th
step only applies to the first non-blank-whitespace and non-plus-sign
character of the input string. So, if I understand those "rules for
parsing non-negative integers", then

<img border="50foo" ...>

or

<img border="50pt" ...>

or

<object border="50bar" ...>

or

<object border="50rem" ...>

should all be rendered the same, that is with a 50px border too on all 4
sides, right?

It seems to me that such "rules for parsing non-negative integers" favor
any string that starts with digits.


I still does not understand how, on one hand, the spec speaks of
"non-conforming", "obsolete" almost everywhere when border attribute is
specified for <img> and <object> but still honors it anyway as in those
testcases. It's a double message, it's a confusing message: it's like
saying "Don't do this ... but, if you do, we'll honor it anyway".


> [1] http://www.whatwg.org/html/#attributes-for-embedded-content-and-images
>
>> When an img element, object element, or input element with a type
>> attribute in the Image Button state is contained within a hyperlink
>> and has a border attribute whose value, when parsed using the _rules
>> for parsing non-negative integers_ [2], is found to be a number greater
>> than zero, the user agent is expected to use the parsed value for
>> eight presentational hints: four setting the parsed value as a pixel
>> length for the element's 'border-top-width', 'border-right-width',
>> 'border-bottom-width', and 'border-left-width' properties, and four
>> setting the element's 'border-top-style', 'border-right-style',
>> 'border-bottom-style', and 'border-left-style' properties to the
>> value 'solid'.
>
> [2] http://www.whatwg.org/html/#rules-for-parsing-non-negative-integers
>
> [3] http://www.w3.org/html/wg/wiki/Testing/Submission/


When I can find more time, I want and will submit 2 testcases about
13.3.10 The hr element
http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html#the-hr-element-0
and margin-left: auto; margin-right: auto; and text-align: [value].

References:

http://lists.w3.org/Archives/Public/public-css-testsuite/2011Jan/0049.html

http://test.csswg.org/suites/css2.1/20101210/html4/margin-left-001.htm

http://test.csswg.org/suites/css2.1/20101210/html4/text-align-006.htm

http://lists.w3.org/Archives/Public/public-css-testsuite/2011Feb/0090.html

Gérard Talbot

Received on Saturday, 1 October 2011 19:41:13 UTC