# \[BUG-6200\]CSS Generation error when no English locale

**URL:** <https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603>\
**Category:** Ignition\
**Tags:** troubleshooting, ignition81, perspective\
**Created:** [June 10, 2022, 10:48am UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603 "2022-06-10T10:48:34Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![jgranada](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jgranada](https://forum.inductiveautomation.com/u/jgranada)\
**Post date:** [June 10, 2022, 10:48am UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/1 "2022-06-10T10:48:34Z")

</div>

When the operating system locale is different from English, the Opacity property of CSS classes forces them with “,” example: "opacity: “0.50” then the browser does not interpret it correctly.

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [June 10, 2022, 12:20pm UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/2 "2022-06-10T12:20:07Z")

</div>

both 0.5 and 0,5 work for me

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 10, 2022, 3:37pm UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/3 "2022-06-10T15:37:13Z")

</div>

Can you provide a screenshot or video of exactly where you’re entering these values and what’s happening that you aren’t expecting?

---

<div class="post-metadata">

**Author:** ![strinidad](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/strinidad/32/10275_2.png) [@strinidad](https://forum.inductiveautomation.com/u/strinidad)\
**Post date:** [June 10, 2022, 5:41pm UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/4 "2022-06-10T17:41:15Z")

</div>

This is the problem that @jgranada have.

I attached a video with the problem.

At the first part you can see, that when the styles are changed from “Style Editor”, the value have a comma instead of a period. This is normal in Spanish locale, but the Style Editor, not translate to the style.css and browser cannot render the value. The designer, also cannot render the value. The icon not change its opacity.

If I add the css property directly to the styles, I can use period or comma with no problems.

In the las part of the video, you can see as the last value entered in the Style Editor of “0,15” with comma is compiled into “style.css”. This value with comma is not working.

If I change the locale of my computer to en-US for example, all works fine.

Regards  
 ![video_css](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/c/5c2f8473ed5c2c087b5ed3eea2f746dfd8cd6ed5.gif)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [June 10, 2022, 8:07pm UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/5 "2022-06-10T20:07:07Z")

</div>

Thanks for the gif @strinidad, I think I understand what’s happening:  
When editing _via the Style Editor_, saved values are ‘localized’ into e.g. `0,15`, which goes directly to the browser and doesn’t work. I filed a ticket to get this investigated and fixed.

---

<div class="post-metadata">

**Author:** ![strinidad](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/strinidad/32/10275_2.png) [@strinidad](https://forum.inductiveautomation.com/u/strinidad)\
**Post date:** [June 10, 2022, 8:22pm UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/6 "2022-06-10T20:22:10Z")

</div>

Exactly this is what happens.

---

<div class="post-metadata">

**Author:** ![strinidad](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/strinidad/32/10275_2.png) [@strinidad](https://forum.inductiveautomation.com/u/strinidad)\
**Post date:** [September 3, 2022, 8:27am UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/7 "2022-09-03T08:27:20Z")

</div>

Any new about this bug ???

Is importart to us, because all opacity and other styles with decimals, cannot be done from designer and we need to change our theme.css

---

<div class="post-metadata">

**Author:** ![strinidad](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/strinidad/32/10275_2.png) [@strinidad](https://forum.inductiveautomation.com/u/strinidad)\
**Post date:** [October 21, 2025, 10:59am UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/8 "2025-10-21T10:59:28Z")

</div>

Hello,

In 8.3 the same error, i don’t know if in 8.1 the problem was solved.

any idea ?

Thanks

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [October 21, 2025, 2:52pm UTC](https://forum.inductiveautomation.com/t/bug-6200-css-generation-error-when-no-english-locale/60603/9 "2025-10-21T14:52:35Z")

</div>

No, the original bug ticket I filed is still waiting to be picked up. At this point any fix will only come to 8.3 or some later version. There is an active effort to improve a bunch of number formatting/internationalization issues _within_ the Perspective application that **might** make this better, but only by accident; it's not intentionally trying to fix this issue.
