297461 - extra '+' signs in MathML testsuite Presentation/TokenElements/mi/miSfontsize9

Status: RESOLVED INVALID

(Core :: MathML, defect)

Description

[Martin Mokrejs]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050612
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050612

There are soem extra `+' signs

Reproducible: Always

Comment 1

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 3

[Martin Mokrejs]

Still extra + signs and the A letter sizes do not match the expected result.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20051122 SeaMonkey/1.5a

./configure --disable-optimize --enable-debug='-g3 -O0' --enable-debug-modules=all --enable-debugger-info-modules --enable-detect-webshell-leaks --enable-svg --enable-svg-renderer-libart --enable-image-decoders=all --with-qtdir=/usr/qt/3 --enable-application=suite --disable-freetype2 --enable-default-toolkit=gtk2 --enable-xft --disable-gssapi

Comment 4

[Martin Mokrejs]

Still an issue with current cvs HEAD build:

./configure --disable-optimize --enable-debug='-g3 -O0 -ggdb' --enable-debug-modules=all --enable-debugger-info-modules --enable-detect-webshell-leaks --disable-svg --enable-image-decoders=all --with-qtdir=/usr/qt/3 --enable-application=suite --disable-freetype2 --enable-jprof --enable-default-toolkit=gtk2 --enable-xft --disable-gssapi

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a2pre) Gecko/20070126 SeaMonkey/1.5a

Comment 5

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

http://www.w3.org/Math/testsuite/build/main/Presentation/TokenElements/mi/miSfontsize9-full.xhtml

I can't see why the "plus" signs should not be displayed. I guess setting the font size to 0.1in (2.54mm) make these symbols very small and that's why they are not visible on the sample rendering.

Comment 6

[Martin Mokrejs]

Attachment: miSfontsize9-full.jpg

Zoom at 100%.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090929 SeaMonkey/1.1.18

Comment 7

[Martin Mokrejs]

Attachment: miSfontsize9-full-200percent.jpg

Zoom at 200%.

Comment 8

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

What are your screenshots supposed to show? In your initial report, you indicate that Mozilla's rendering contains extra '+' signs, what make you think that they should not be there? I can't see from the source code of the test why some "+" be invisible. I only see that they must be small, as I said in comment 5.

Comment 9

[Martin Mokrejs]

Frederic, you are probably right. I just wanted to post what I get.

Comment 10

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

(In reply to comment #9)
> Frederic, you are probably right. I just wanted to post what I get.

In the description you give in comment 0, you simply indicate that there are extra `+' signs (but this is not reflected in the bug title, where you give the test title). So if you agree that the sample rendering is incorrect, I would suggest closing this bug.

However in comment 3, you are also talking about issues for the size of the A's so I guess your initial goal was to report that Mozilla's rendering does not match the sample rendering. Again, I don't know if we can rely on the testsuite screenshot. We should rather study carefully the font* attribute values and see what is really expected. Hence we will be able to confirm / invalidate this bug.

Comment 11

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

Note: this bug was mentioned in bug 449396, I've not checked whether they are related.

Comment 12

[Martin Mokrejs]

I went to test old binaries and downloaded old binary releases of seamonkey-1.0, 1.0.4, 1.1.4. Unfortunately, all rendered the test page as raw <math> sources with the embedded image. In the end I tried with current 1.1.18 I get same source code displayed. It look the target page has some problems. This is what I have in error console.

Warning: reference to undefined property Components.classes['@modifyheaders.mozdev.org/service;1']
Source file: chrome://modifyheaders/content/modifyheaders.js
Line: 2
 ----------
Error: Components.classes['@modifyheaders.mozdev.org/service;1'] has no properties
Source file: chrome://modifyheaders/content/modifyheaders.js
Line: 2
 ----------
Warning: reference to undefined property Components.classes['@maone.net/noscript-service;1']
Source file: chrome://noscript/content/noscript.js
Line: 8
 ----------
Warning: reference to undefined property Components.classes['@maone.net/noscript-service;1']
Source file: chrome://noscript/content/noscript.js
Line: 8
 ----------
Error: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]
Source file: chrome://imagezoom/content/ZoomImageManager.js
Line: 5
 ----------
Error: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]
Source file: chrome://imagezoom/content/overlay.js
Line: 46
 ----------
Warning: Error in parsing value for property 'white-space'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/global.css
Line: 260
 ----------
Warning: Error in parsing value for property 'white-space'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/global.css
Line: 262
 ----------
Warning: Error in parsing value for property 'white-space'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/global.css
Line: 263
 ----------
Warning: Unknown property '_overflow'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/yui/calendar.css
Line: 7
 ----------
Warning: Unknown property '_height'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/show_bug.css
Line: 98
 ----------
Warning: Unknown property '_position'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/show_bug.css
Line: 102
 ----------
Warning: Unknown property 'filter'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/yui/autocomplete.css
Line: 7
 ----------
Warning: Unknown property 'filter'.  Declaration dropped.
Source file: https://bugzilla.mozilla.org/skins/standard/yui/autocomplete.css
Line: 7
 ----------
Warning: anonymous function does not always return a value
Source file: https://bugzilla.mozilla.org/js/yui/yahoo-dom-event.js
Line: 7, Column: 94
Source code:
this.getXY(U);if((R[0]!==null&&S[0]!=R[0])||(R[1]!==null&&S[1]!=R[1])){this.setXY(U,R,true);}}};B.Dom.batch(O,P,B.Dom,true);},setX:function(P,O){B.Dom.setXY(P,[O,null]);},setY:function(O,P){B.Dom.setXY(O,[null,P]);},getRegion:function(O){var P=function(Q)
 ----------
Warning: test for equality (==) mistyped as assignment (=)?
Source file: https://bugzilla.mozilla.org/js/yui/yahoo-dom-event.js
Line: 7, Column: 52
Source code:
tion(O){var P=function(Q){if(L){while(Q=Q.parentNode){if(Q==document.documentElement){return true;}}return false;}return this.isAncestor(document.documentElement,Q);};return B.Dom.batch(O,P,B.Dom,true);},getElementsBy:function(V,P,Q,S){P=P||"*"; 
 ----------
Warning: test for equality (==) mistyped as assignment (=)?
Source file: https://bugzilla.mozilla.org/js/yui/yahoo-dom-event.js
Line: 8, Column: 203
Source code:
(){var O=self.innerWidth;var P=document.compatMode;if(P||G){O=(P=="CSS1Compat")?document.documentElement.clientWidth:document.body.clientWidth;}return O;},getAncestorBy:function(O,P){while(O=O.parentNode){if(D(O,P)){return O;}}return null;},getAncestorByC
 ----------
Warning: anonymous function does not always return a value
Source file: https://bugzilla.mozilla.org/js/yui/calendar.js
Line: 7, Column: 176
Source code:
var E=this.config[D];if(E&&E.event){if(this.initialConfig[D]&&!B.isUndefined(this.initialConfig[D])){this.setProperty(D,this.initialConfig[D]);return true;}}else{return false;}},setProperty:function(E,G,D){var F;E=E.toLowerCase();if(this.queueInProgress&&
 ----------
Error: keywordAutoComplete.textboxFocusEvent has no properties
Source file: https://bugzilla.mozilla.org/show_bug.cgi?id=297461
Line: 1412
 ----------
Warning: reference to undefined property Components.classes['@modifyheaders.mozdev.org/service;1']
Source file: chrome://modifyheaders/content/modifyheaders.js
Line: 2
 ----------
Error: Components.classes['@modifyheaders.mozdev.org/service;1'] has no properties
Source file: chrome://modifyheaders/content/modifyheaders.js
Line: 2
 ----------
Warning: reference to undefined property Components.classes['@maone.net/noscript-service;1']
Source file: chrome://noscript/content/noscript.js
Line: 8
 ----------
Warning: reference to undefined property Components.classes['@maone.net/noscript-service;1']
Source file: chrome://noscript/content/noscript.js
Line: 8
 ----------
Error: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]
Source file: chrome://imagezoom/content/ZoomImageManager.js
Line: 5
 ----------
Error: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]
Source file: chrome://imagezoom/content/overlay.js
Line: 46
 ----------
Warning: reference to undefined property Components.classes[contractid]
Source file: chrome://global/content/autocomplete.xml
Line: 116

Comment 13

[Martin Mokrejs]

(In reply to comment #10)
> (In reply to comment #9)
> > Frederic, you are probably right. I just wanted to post what I get.
> 
> In the description you give in comment 0, you simply indicate that there are
> extra `+' signs (but this is not reflected in the bug title, where you give the
> test title). So if you agree that the sample rendering is incorrect, I would
> suggest closing this bug.
> 
> However in comment 3, you are also talking about issues for the size of the A's
> so I guess your initial goal was to report that Mozilla's rendering does not
> match the sample rendering. Again, I don't know if we can rely on the testsuite
> screenshot. We should rather study carefully the font* attribute values and see
> what is really expected. Hence we will be able to confirm / invalidate this
> bug.

I had a look into the History of this bug report. I think I really reported that two 'A's were next to each other. Because you studied the sources and see no reason for a failure and I could not reproduce that in comments #6 and #7 feel free to close this.

And, my apologies for the list of errors from the error console. I do not know where they came from as it was a freshly started browser. But when I reload the page with error console cleared I do not get them. However, I see only the <math> source code. But that has nothing to do with those errors. Sorry.

Comment 14

[Martin Mokrejs]

(In reply to comment #13)
> (In reply to comment #10)
> > (In reply to comment #9)
> > > Frederic, you are probably right. I just wanted to post what I get.
> > 
> > In the description you give in comment 0, you simply indicate that there are
> > extra `+' signs (but this is not reflected in the bug title, where you give 
> that two 'A's were next to each other. Because you studied the sources and see

Two plus signs.