# Perspective - Numeric Input Value Component BUG?

**URL:** <https://forum.inductiveautomation.com/t/perspective-numeric-input-value-component-bug/35908>\
**Category:** Ignition Early Access\
**Created:** [June 23, 2020, 11:41am UTC](https://forum.inductiveautomation.com/t/perspective-numeric-input-value-component-bug/35908 "2020-06-23T11:41:21Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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:** [April 5, 2023, 3:02pm UTC](https://forum.inductiveautomation.com/t/perspective-numeric-input-value-component-bug/35908/10 "2023-04-05T15:02:35Z")

</div>

If you only need these rules in one area, you're better served targeting the specific component.

```auto
/* Chrome, Safari, Edge, Opera */
#myTargetDomId input::-webkit-outer-spin-button,
#myTargetDomId input::-webkit-inner-spin-button {
  -webkit-appearance: none;
  margin: 0;
}

/* Firefox */
#myTargetDomId input[type=number] {
  -moz-appearance: textfield;
}

```

Couple this with use of the `meta.domId` property to target an individual component.  
 ![Screenshot 2023-04-05 at 8.01.37 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/9/19b03a0afdc0fc168ce75b85a61d39fce51290a0.png)  
 ![Screenshot 2023-04-05 at 8.01.55 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/a/fa79308e6827fae0bdf2fdf6dec88e18be79ded2.png)

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-numeric-input-value-component-bug/35908)._