470396 - CSS generated counters handled inconsistently

Status: RESOLVED INVALID

(Core :: CSS Parsing and Computation, defect)

Description

[Marcin Szychowski]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9.0.3) Gecko/2008092416 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9.0.3) Gecko/2008092416 Firefox/3.0.3

CSS generated counters require initialization by {counter-reset: counterName;} property (as widely discussed under bug 288946). Otherwise counter won't increment, displaying '1' along the document.

However applying {counter-increment: counterName;} to tr (and maybe others) elements results in 'proper' (?) counter implementation.

See attachments

Reproducible: Always

Steps to Reproduce:
1. Open attachment 1 [details] [diff] [review]
2. Open attachment 2 [details] [diff] [review]
3. Compare sources
Actual Results:  
Firefox treats td and tr elements inconsistently, allowing incrementation of uninitialized (not yet reset) counters on tr elements, while not incrementing such counters 

Page 1 displays:
1.
1.
1.
1.

Page 2 displays:
1.
2.
3.
4.


Expected Results:  
Both Page 1 and Page 2 should display the same, shouldn't them?

Please do not mark this bug as duplicate of 288946 too quickly.

Comment 1

[Marcin Szychowski]

Attachment: example Page 1

Counter is not reset and is not incremented on td, td.someclass elements

Comment 2

[Marcin Szychowski]

Attachment: example Page 2

Counter is not reset, however increments on tr elements

Comment 3

[Marcin Szychowski]

Problem persists as of Fx 3.0.5

Comment 4

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

The counter-increment on the TR elements establishes a scope on the TBODY, so this behavior seems correct to me.

If you disagree, please describe which testcase you think should be handled differently and what you think the results should be.