Bug 34708 – The number displays incorrectly if counter-increment is with an identifier and a number equivalent to the maximum value 2147483647 and grouped thirty-two times.

• Component: CSS
• Status: RESOLVED CONFIGURATION CHANGED

Use Case:
Counter-increment with an identifier and a number equivalent to the maximum
value, ident 2147483647, grouped thirty-two times.
Counter-increment with an identifier and a number equivalent to the maximum
value with a plus sign, ident [phone], grouped thirty-two times.
Counter-increment with an identifier and a number equivalent to the maximum
minus one value, ident 2147483646, grouped thirty-two times.
Counter-increment with an identifier and a number equivalent to the maximum
plus one value, ident 2147483648, grouped thirty-two times.


1. Launch QtLauncher.
2. Unzip the contents of the zip file.
3. Load the html page from the extracted zip file.
4. Click on the first link on the page.

Actual outcome:
The number is -32.

Expected outcome:
The number should be 2147483647.

Created attachment 48337 [details]
test case

[Tor Arne Vestbø]

Please follow the QtWebKit bug reporting guidelines when reporting bugs.

See http://trac.webkit.org/wiki/QtWebKitBugs

Specifically:

  - The 'QtWebKit' component should only be used for bugs/features in the
    public QtWebKit API layer, not to signify that the bug is specific to
    the Qt port of WebKit

      http://trac.webkit.org/wiki/QtWebKitBugs#Component

  - Add the keyword 'Qt' to signal that it's a Qt-related bug

      http://trac.webkit.org/wiki/QtWebKitBugs#Keywords

[Robert Hogan]

Test links are:

http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-050.htm
http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-051.htm
http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-049.htm
http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-052.htm

All fail, giving either -32 or -64, on Chromium and Qt Launcher - so looks like a WebCore CSS bug.

[Alexey Proskuryakov]

> http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-050.htm
> http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-051.htm
> http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-049.htm
> http://www.w3.org/Style/CSS/Test/CSS2.1/20100127/html4/counter-increment-052.htm

These all pass in ToT WebKit with Safari (64 bit). Should the tests be imported?

[Ahmad Saleem]

I am unable to reproduce this bug using the test cases from CSS2.1 test suite listed in Comment 03, Safari 15.6.1 passes all of them and show expected result similar to all other browsers (Chrome Canary 106 and Firefox Nightly 105).

I am going to mark this as "RESOLVED CONFIGURATION CHANGED", please reopen if you think it is incorrect testing or this is not resolved. Thanks!