Opened 12 years ago

Closed 11 years ago

Last modified 10 years ago

#8250 closed defect (invalid)

double byte comma used in FF number formatting but not IE

Reported by: richso Owned by: anonymous
Priority: high Milestone: tbd
Component: General Version: 1.1.1
Keywords: Cc:
Blocked By: Blocking:


double byte comma is used in FF while single byte comma used in IE

Change History (8)

comment:1 Changed 12 years ago by richso

I mean in number formatting

comment:2 Changed 12 years ago by Adam Peller

will need a lot more information. could you please provide a test case? If you're talking about dojo.number, which locale? what's a double byte comma?

comment:3 Changed 12 years ago by bill

He's referring to the full-width comma (twice the width of these characters). It should be visible just by looking at test_validate.html in Japanese or maybe Chinese locale... although when I tried to switch my locale it seemed like the numbers were full-width rather than the comma.

Also, not sure what "correct" behavior is; I would think half-width for both numbers and commas.

comment:4 Changed 12 years ago by bill

Oh maybe an example is better, if this shows up: 123,456 vs 123,456

comment:5 Changed 12 years ago by Adam Peller

Thanks, that's helpful, though it sounds like you're also having trouble reproducing the problem, so specifics are important: test page, locale, browser version, etc.

comment:6 in reply to:  4 Changed 12 years ago by richso

Replying to bill:

Oh maybe an example is better, if this shows up: 123,456 vs 123,456

min our locale zh-tw (big5)

123,456 (FF) 123,456 (IE6,7)

comment:7 Changed 12 years ago by Adam Peller

In the future, a full, running example is really what we need. There's still some ambiguity here -- does the number appear in a control or in HTML? What encoding is involved? (is it really big5 vs. UTF-8?) What platform are you running on? Etc.

I see plain 123,456 on both browsers on Windows and FF on Mac. I wonder if there's something special going on to accomodate your system if it's set up with certain regional packages, or perhaps Firefox tries to normalize numerals in some instances? I seem to recall FF having magic to convert numbers to Hindi for Arabic documents. So it might take a lot more information to reproduce this.

You may wish to try putting "123,456" (plain ASCII) in a document in the same manner you're using dojo.number formatting and see how the browsers represent these numbers independent of Dojo.

comment:8 Changed 11 years ago by Adam Peller

Resolution: invalid
Status: newclosed

Please reopen with a specific test case and full platform information necessary to reproduce, as requested above. Browser version? Do regional patches or features need to be installed for bidi? etc. Thanks.

Note: See TracTickets for help on using tickets.