Summary: | 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. | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | sangeetha.sugavanam | ||||
Component: | CSS | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED CONFIGURATION CHANGED | ||||||
Severity: | Normal | CC: | ahmad.saleem792, ap, bfulgham, igor.oliveira, rniwa, robert, simon.fraser, zalan | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Attachments: |
|
Description
sangeetha.sugavanam
2010-02-08 09:12:04 PST
Created attachment 48337 [details]
test case
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 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. > 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?
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! |