# \[Bug-12999\]Perspective numeric entry does not obey format string

**URL:** <https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086>\
**Category:** Ignition Early Access\
**Created:** [March 6, 2019, 4:07am UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086 "2019-03-06T04:07:07Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [May 13, 2020, 3:33pm UTC](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086/4 "2020-05-13T15:33:50Z")

</div>

It turns out that both of your questions regard expected behaviors.

The format is only applied on a visual level so as not to change any value coming in (we don’t want to change values you supply - only how they’re visually represented).

As for removing the arrows, Yousuf recommends using this: [https://www.w3schools.com/howto/howto\_css\_hide\_arrow\_number.asp](https://www.w3schools.com/howto/howto_css_hide_arrow_number.asp)

Before the theming update we had removed them from Chrome but not Firefox. It sounds like going forward we’re going to be more hands-off since we’re allowing and encouraging customers to develop their own CSS. AS a result, we’ve removed the Chrome-specific removal of the arrows.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-12999-perspective-numeric-entry-does-not-obey-format-string/23086)._
