This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9100 - Crash with CSS counters
Summary: Crash with CSS counters
Status: REOPENED
Alias: None
Product: Amaya
Classification: Unclassified
Component: CSS (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 critical
Target Milestone: ---
Assignee: Vincent Quint
QA Contact: Vincent Quint
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-20 19:03 UTC by fred.wang
Modified: 2012-08-24 05:57 UTC (History)
6 users (show)

See Also:

Attachments
Crash test (247 bytes, application/xhtml+xml)
2010-02-20 19:03 UTC, fred.wang 		Details

Description fred.wang 2010-02-20 19:03:20 UTC 
Created attachment 825 [details]
Crash test

I was trying to use CSS counters to annotate MathML formulas with numbers and I discovered a crash. I give a reduced testcase (see attachment).
Comment 1 fred.wang 2010-02-22 17:10:55 UTC 
Thanks Vincent. The crash no longer happens, but it seems that there is now a problem with counters (I'm not sure, but I don't remember having seen it before your commit). To annotate formulas, I use

math[display="block"]:after {
  content: "(" counter(chapter) "." counter(formula) ")";
}

but the counter "chapter" is always 0 when used in this context. The strange thing is that "chapter" takes the right value when used in headers. I've the same problem with the counter "figure".

See http://www.cs.au.dk/~fwang/speciale/report/content.xhtml
Comment 2 Vincent Quint 2010-02-22 17:34:20 UTC 
I'll investigate this further, but I suspect the problem comes from using several namespaces in conjonction with counters. Here, the selector uses elements and attributes from the MathML namespace, whereas the content is based on a counter that is incremented by elements from the HTML namespace (I guess). This may well confuse Amaya. I'll try to resolve that soon.