User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030327 Debian/1.3-4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030327 Debian/1.3-4 If I call format-number function for a node, in which is a positive number, a negative with the same value is displayed( -3 instead of 3 ). See Attachment for example. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: wrong number is diplayed( -3) Expected Results: 3
Created attachment 118831 [details] Document, which reproduce the bug It shows -3, but it should show 3.
Created attachment 118832 [details] stylesheet with broken format-number I call format-number for the a element. This call makes the number negative, but shouldn't. XML to this XSL is in Attachment 118831 [details].
Created attachment 118834 [details] Testcase (part 2 of 2) This testcase references attachment 118832 [details] inline.
Attachment #118831 - Attachment is obsolete: true
:( Don't know what I did to foul that testcase up, but in a local-file test I get an HTML document displaying the number 3, not -3. WFM Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4a) Gecko/20030328
Attachment #118832 - Attachment mime type: text/xsl → text/xml
This Works For Me too
I've downloaded the latest build (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030328), and it works fine. I'm sorry to disturb you. I'll wait for the next Debian build, and if there's still the bug, i'll report it to Debian. I'm sorry.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
marking verified. Jan: which version were you using when you ran into this bug? I can't remember that we've ever had a problem like the one you describe.
Status: RESOLVED → VERIFIED
It is version from Debian package mozilla-browser 2:1.3-4. It says about itself: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030327 Debian/1.3-4 I don't know anything more. URL for this package:http://packages.debian.org/unstable/web/mozilla-browser.html
You need to log in before you can comment on or make changes to this bug.