# Can chrome extensions read component properties?

**URL:** <https://forum.inductiveautomation.com/t/can-chrome-extensions-read-component-properties/91990>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 18, 2024, 4:39am UTC](https://forum.inductiveautomation.com/t/can-chrome-extensions-read-component-properties/91990 "2024-06-18T04:39:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![abelew](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@abelew](https://forum.inductiveautomation.com/u/abelew)\
**Post date:** [June 18, 2024, 4:39am UTC](https://forum.inductiveautomation.com/t/can-chrome-extensions-read-component-properties/91990/1 "2024-06-18T04:39:35Z")

</div>

I'm investigating the possibility of writing an OSK extension for chrome to use with Perspective. Is there any way that an extension would be able to read the min/max values for a numeric entry field? does that information make it into the browser, or is that all server-side?

---

<div class="post-metadata">

**Author:** ![abelew](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@abelew](https://forum.inductiveautomation.com/u/abelew)\
**Post date:** [June 20, 2024, 4:49pm UTC](https://forum.inductiveautomation.com/t/can-chrome-extensions-read-component-properties/91990/4 "2024-06-20T16:49:41Z")

</div>

What part of the html did you find that in? It looks a lot different than what i was seeing.

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/c/0c56993f6a1a309d1462ebbaa569ba48b3992c52.png)

---

<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 21, 2024, 6:37am UTC](https://forum.inductiveautomation.com/t/can-chrome-extensions-read-component-properties/91990/5 "2024-06-21T06:37:55Z")

</div>

Oops thats that was a custom component.  
My bad seems its not in the html itself...

You could acces it through the client and read the props though.  
If you have a click event from the input. yuo can find the "main" element that has a 'data-component-path' property. which you can use to find the view and after that to find its child component and props

```python
const view = [...window.__client.page.views._data.values()].find(view => view.value.mountPath == this.closest('[data-component-path]').getAttributeNode('data-component-path').value.split('.')[0]).value; 

```

(i used the path directly here in the console script as i dont have an event setup)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/a/7aad02618a5e892cee7fc710f42a95507ae8a92b.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/f/ef7ee5ce0adf269bc23aeea34b8584bac42ae992.png)

If you found the component you can request it props.  
You'll have to write something smart to find the correct child with the `addressPathString` yourself though ;p Its gonna get a bit harder with embeded views too i if i remember correctly(i dont remeber if my view selector handles it already or not)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/8/a8d52eb8685daf2f9a1f6547dcb11c55235e96c2.png)