Bug 31814 – Inconsistent use of counterName and identifier in CSS counter code and loss of information about the counter type.

• Status: RESOLVED
• Resolution: FIXED
• Component: CSS

[Carol Szabo]

Patch coming soon.

[Carol Szabo]

Created attachment 44587 [details]
Proposed Patch

Added accessors and members to the CounterNode class to differentiate between reset type nodes and nodes that act as reset because they are not in the scope of any other counter node with the same identifier. This is useful in reevaluating the values of counters when new counters are added to the DOM that may make a root node non-root.
Changed references to counterName to identifier for consistency.

[WebKit Review Bot]

style-queue ran check-webkit-style on attachment 44587 [details] without any errors.

[Darin Adler]

Comment on attachment 44587 [details]
Proposed Patch

> +    // identifier must match the identifier of this counter.
>      void removeChild(CounterNode*, const AtomicString& identifier);

The comment here is worded strangely. You say it must match. That makes it sound like it's a programming mistake if I pass an identifier that does not match. I don't think that's how it works.

Maybe this wording: "Does nothing unless the identifier matches the identifier of the counter."

Or maybe you can think of something better.

r=me

[WebKit Commit Bot]

Comment on attachment 44587 [details]
Proposed Patch

Clearing flags on attachment: 44587

Committed r52450: <http://trac.webkit.org/changeset/52450>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.