# Perspective Icons sometimes have a stroke

**URL:** <https://forum.inductiveautomation.com/t/perspective-icons-sometimes-have-a-stroke/73446>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [May 9, 2023, 3:43am UTC](https://forum.inductiveautomation.com/t/perspective-icons-sometimes-have-a-stroke/73446 "2023-05-09T03:43:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carl\_Geib](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@Carl\_Geib](https://forum.inductiveautomation.com/u/Carl_Geib)\
**Post date:** [May 9, 2023, 3:43am UTC](https://forum.inductiveautomation.com/t/perspective-icons-sometimes-have-a-stroke/73446/1 "2023-05-09T03:43:31Z")

</div>

Currently working on a project, using Ignition 8.1.25.

I've noticed sometimes my icon objects have a stroke, and other times they don't.

As an example, I've created view with an SVG valve graphic and I am using it as a template/symbol on other pages. I use an icon on the template to indicate a failure/alarm (just bind the visibility tag to an alarm status). Sometimes the icon has a stroke on template and sometimes it doesn't. It's the exact same template, just a different parameter for the valve tag. The icon object doesn't even have an option for a stroke, and if you try and add one it doesn't seem to work. The stroke seems to occur randomly at times, and then without even making changes (that I can recall) it will go away again at some point.

I've seen this happen in the Designer, Firefox, Chrome, and Perspective Workstation.

 ![PerspectiveIcon_Stroke_Issue](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/d/2d6aaf10a3b969f6b17eb4d479ab00eca4a0c5d2.png)

Anyone seen this before or have any thoughts. I tried doing a search through the forums and wasn't seeing anyone else having this issue.

---

<div class="post-metadata">

**Author:** ![Matthew.gaitan](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@Matthew.gaitan](https://forum.inductiveautomation.com/u/Matthew.gaitan)\
**Post date:** [May 9, 2023, 3:54pm UTC](https://forum.inductiveautomation.com/t/perspective-icons-sometimes-have-a-stroke/73446/2 "2023-05-09T15:54:09Z")

</div>

Does the icon have any style / style classes applied to it, other than it's color?

Do you have any style / style classes applied at a higher level in the view holding the icon?

To get rid of the stroke on only the Icon you can change the icons style to:

```auto
{
  "stroke": "none"
}

```

If you always want a stroke on the icon try:

```auto
{
  "stroke": "black !important",
  "strokeWidth": "1px !important"
}

```

---

<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:** [May 9, 2023, 5:03pm UTC](https://forum.inductiveautomation.com/t/perspective-icons-sometimes-have-a-stroke/73446/3 "2023-05-09T17:03:31Z")

</div>

You can also always open your browser's dev tools and see the live style actually being applied, and usually where it's coming from; e.g. a style class will have a `.psc-` prefix on the selector.

---

<div class="post-metadata">

**Author:** ![Carl\_Geib](https://avatars.discourse-cdn.com/v4/letter/c/d78d45/32.png) [@Carl\_Geib](https://forum.inductiveautomation.com/u/Carl_Geib)\
**Post date:** [May 9, 2023, 10:00pm UTC](https://forum.inductiveautomation.com/t/perspective-icons-sometimes-have-a-stroke/73446/4 "2023-05-09T22:00:05Z")

</div>

@paul-griffith I've actually used the browsers dev tools in the past, but it's been a chaotic couple of weeks, and it just didn't occur to me.

Using the dev tools I was able to track it down to a style being applied on a parent div. In this instance specifically a stroke got applied to a couple of the view's dropped on the screen and a stroke was being applied to the entire view. It's not clear to me why/how a stroke was applied those views, but hopefully it was just a random mistake, and this appears to be resolved for the time being. Appreciate the help.