User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
Theoretically, a <mml:math><mml:mi>x</mml:mi></mml:math>-Achse can be broken
into two lines: the "x", and the "-Achse"
Steps to Reproduce:
The whole expression must be kept together. If non-whitespace is directly
attached to the inline formula, the must not be any break between the
non-whitespace and the formula.
May be related to bug 172819.
Created attachment 151823 [details]
This is a testcase which demonstrates, that this error has been solved. ...
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
It's reproducible with Firefox 1.0.7, it's still a bug, it still should be
fixed, and this is a stange method for finding bugs that are worth being fixed
(whatever this means).
Created attachment 406778 [details]
Test vertical alignement with stretchy ops
In the case symmetric="false", I suppose the vertical bar should have its center aligned with the centers of red mspace's, but here the bottoms are aligned.
Created attachment 406781 [details]
Created attachment 406782 [details]
Screenshot of the testcase
(Please ignore comment 4)
I attached an updated testcase and a screenshot that shows that the bug still happens. But is it really a bug? I've not checked what the spec says.
This still happens in firefox 3.5.3 (fedora 11, x86_64).
Is it a bug? Yes; the intent is that <math display="inline"> should
act like any inline element; <math display="block"> like a block element.
The MathML 2 specification perhaps wasn't as explicit about this
as it could have been, but we are hoping the MathML 3 spec
(currently in last call) will be clearer.
Created attachment 407349 [details]
Sorry, I previously attached the wrong file.
Created attachment 407350 [details]
Testcase, with <math/> replaced by a <span/>
Created attachment 424860 [details]
Created attachment 424861 [details]
Expected result (Amaya)
"Moreover, when the math element is embedded in a larger document, a block math element should be treated as a block element as appropriate for the document type (typically as a new vertical block), whereas an inline math element should be treated as inline (typically exactly as if it were a sequence of words in normal text). In particular, this applies to spacing and linebreaking: for instance, there should not be spaces or line breaks inserted between inline math and any immediately following punctuation."
*** Bug 422619 has been marked as a duplicate of this bug. ***
BTW, another quite common situation is when the inline math is followed by a punctuation marks. For example a comma or a period can be moved at the beginning of a new line, which is really not expected.
Let me add some real cases, from the journal I work for:
In Firefox that the renderer is inconsistent in deciding whether
to break before or after a relational operator. In TeX, inline math
breaks after. Also it allows breaks just before the argument of a
function. Finally (a different bug), the delimiters in the displayed
equation are sometimes ridiculously large.
one can see a break just _after_ a parenthesis.
I would emphasize that the desired solution to this is _not_ to
add additional tags in the mathml such as nobreak. Mathml is supposed
to describe the math content, not how it is laid out. It is the
browser's job to render it correctly. I assume this is possible in
the cases above, because TeX is perfectly capable of choosing the
correct breaks in (say) $(x+y)+z=x+(y+z)$ (with much less verbosity).
(In reply to comment #16)
> Let me add some real cases, from the journal I work for:
> In Firefox that the renderer is inconsistent in deciding whether
> to break before or after a relational operator. In TeX, inline math
> breaks after. Also it allows breaks just before the argument of a
> function. Finally (a different bug), the delimiters in the displayed
> equation are sometimes ridiculously large.
> one can see a break just _after_ a parenthesis.
Okay, but this is another bug. What you desire is better line breaks *within* the inline MathML. This is probably even a very different place in the source code.
> Okay, but this is another bug. What you desire is better line breaks *within*
> the inline MathML. This is probably even a very different place in the source
Right, this is what Matthew reported in bug 508120 (that I've just renamed to make clear it is about line break within MathML formulas)