Bug 26984

Summary: style properties depend on locale.
Product: WebKit Reporter: arno. <a.renevier>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: jmalonzo
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
testcase none

arno.
Reported 2009-07-05 14:05:25 PDT
Hi, style properties (as read with javascript) depend on locale. For example, following piece of code: p.style.width = '100.5px'; alert(p.style.width); show 100,5px with a french locale and 100.5px with an english locale (decimal separator is not the same). That makes comparaison and parsing of those results nearly impossible in a cross-locale way. Moreover, as parseFloat is not locale dependant, p.style.opacity = 0.5; parseFloat(p.style.opacity); shows 0 with a french locale and 0.5 with an english locale. That's quite disturbing. Setting to gtk component as I don't known if it happens with other backends.
Attachments
testcase (476 bytes, text/html)
2009-07-05 14:07 PDT, arno. 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
arno.
Comment 1 2009-07-05 14:07:00 PDT
Created attachment 32282 [details] testcase
Jan Alonzo
Comment 2 2009-07-06 04:39:22 PDT
(In reply to comment #0) > Hi, > style properties (as read with javascript) depend on locale. > For example, following piece of code: > > p.style.width = '100.5px'; > alert(p.style.width); > > show 100,5px with a french locale and 100.5px with an english locale (decimal > separator is not the same). > That makes comparaison and parsing of those results nearly impossible in a > cross-locale way. > Moreover, as parseFloat is not locale dependant, > > p.style.opacity = 0.5; > parseFloat(p.style.opacity); > > shows 0 with a french locale and 0.5 with an english locale. > That's quite disturbing. > > Setting to gtk component as I don't known if it happens with other backends. *** This bug has been marked as a duplicate of bug 18994 ***
Note You need to log in before you can comment on or make changes to this bug.