346222 - CSS errors when you load a MathML page that uses -moz-* selectors

Status: RESOLVED WORKSFORME

(Core :: MathML, defect)

Description

[steve.swanson]

When I load a MathML page I see

CSS Error (resource://gre/res/mathml.css :69.19): Unknown pseudo-class or pseudo
-element '-moz-math-inline'.  Ruleset ignored due to bad selector.
CSS Error (resource://gre/res/mathml.css :436.21): Unknown pseudo-class or pseud
o-element '-moz-math-stretchy'.  Ruleset ignored due to bad selector.
CSS Error (resource://gre/res/mathml.css :441.22): Unknown pseudo-class or pseud
o-element '-moz-math-anonymous'.  Ruleset ignored due to bad selector.

I first saw this problem in June, but MathML was blocked by bug 342533.

Comment 1

[Jesse Ruderman]

Regression from bug 331883?  (See bug 331883 comment 17.)

Comment 2

[Boris Zbarsky [:bzbarsky]]

Is this still an issue?  This looks like a duplicate of bug 342961....

Comment 3

[Boris Zbarsky [:bzbarsky]]

Actually, ignore the comment about bug 342961.  Comment 1 is right on the money...  No wonder I couldn't get the TeX integral signs on the MathML test pages on Mozilla.org...

Comment 4

[Jesse Ruderman]

Will the fix for bug 347303 fix this bug?

Comment 5

[Boris Zbarsky [:bzbarsky]]

No, since the author sheets for this page style the -moz pseudos in question.  That fix will fix the errors listed in comment 0, but there are other errors on this page too.

Comment 6

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Attachment: easy fix

This fixes loading of agent sheets via the doctype to allow unsafe rules in those sheets.

Loading the start.xhtml URL, there are still warnings about -moz-* selectors being used in author sheets. I don't know why they need to be there, because I assume authors should not need to use -moz-* selectors. If authors do need these selectors then someone can file a new bug about that and explain why.

Comment 7

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Comment on attachment 232078 [details] [diff] [review]
easy fix

Never mind, Boris already submitted this patch in another bug.

I don't want to worry about the author warnings until someone explains why authors need to use these selectors.

Comment 8

[Jesse Ruderman]

Morphing slightly to distinguish this bug from bug 347303.

Comment 9

[rbs]

Re:Comment #7

It is an extra, albeit non critical. It used to be that you could style/set which stretchy fonts in different parts of a document. For example,

[class="TeX"] mo[class="TeX"]::-moz-math-stretchy {
   font-family: CMSY10, CMEX10;
}
[class="Mathematica"] mo[class="Mathematica"]::-moz-math-stretchy {
   font-family: Math1, Math2, Math4;
}
[...]
<p class='TeX'>
  all <math>...</math> here will use Mathematica fonts for stretchy chars
</p>
...and in the _same_ document...
<p class='Mathematica '>
  all <math>...</math> here will use Mathematica fonts for stretchy chars
</p>

====
And you could even do
<mrow>
  <mo class='TeX'>)</mo> <!-- left parenthesis is stretched with TeX fonts --->
  <mrow> something tall here </mo>
  <mo class='Mathematica'>)</mo> <!-- right parenthesis is stretched with Mathematica fonts --->
</mrow>

[Therefore, allowing for cool demos, or to really visually contrast the glyphs and confound the sceptics as to the beauty of a particular font distro :-)]

Without the -moz, it is not possible to do that anymore. But it is not really critical, if the -moz is not possible due to security concerns higher up in the product.

Comment 10

[Boris Zbarsky [:bzbarsky]]

rbs, could there be issues if these stretchy chars got styled in "weird" ways (positioned, floated, display: none, whatever)?

I don't really care whether we change the treatment of the stretchy selectors in author sheets, but we need to make the demos on mozilla.org work; if that means changing the CSS in those demos to use a different selector, we should do so.

Comment 11

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

Minusing for blocking1.8.1 -- we've shipped a bunch of 1.8.0.x release with it already.  It would be nice to have, though, and we'll consider a patch.

Comment 12

[Daniel Veditz [:dveditz]]

ditto comment 11 for 1.8.0.7 -- would love a patch.

Comment 13

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Boris' patch in bug 347303 fixes the most important issues here and he's requested approval for 1.8.0.7 in that bug.

Comment 14

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

What's still broken here?  Anything?

Comment 15

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

Minusing for blocking1.9.  Renominate if you have a better explanation of what problems are currently present on the trunk and you think that explanation deserves consideration for blocking/wanted.

Comment 16

[Michael Kohler [:mkohler]]

This is a mass change. Every comment has "assigned-to-new" in it.

I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.

Comment 17

[Frédéric Wang (:fredw)]

(In reply to David Baron [:dbaron] from comment #14)
> What's still broken here?  Anything?

Last time I tried to load the MathML demos, I got

- Unknown pseudo-element or pseudo-class :-moz-math-font-style-stretchy
- Unknown pseudo-element or pseudo-class ::-moz-math-stretchy

The -moz-math-font-style-stretchy selector has been removed from the demo pages in bug 557481. I thought we would have to modify something in Gecko to indicate that using -moz-math-stretchy is safe and hence make the warning disappear. However, I no longer get any warning now.