# Adding Phoenix.LiveView.JS function for getting \`getBoundingClientRect\` params

**URL:** <https://forum.elixirforum.com/t/adding-phoenix-liveview-js-function-for-getting-getboundingclientrect-params/65504>\
**Category:** Proposals: Ideas\
**Tags:** phoenix, liveview\
**Created:** [August 15, 2024, 12:55pm UTC](https://forum.elixirforum.com/t/adding-phoenix-liveview-js-function-for-getting-getboundingclientrect-params/65504 "2024-08-15T12:55:25Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![shahryarjb](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/shahryarjb/32/39485_2.png) [@shahryarjb](https://forum.elixirforum.com/u/shahryarjb)\
**Post date:** [August 15, 2024, 3:17pm UTC](https://forum.elixirforum.com/t/adding-phoenix-liveview-js-function-for-getting-getboundingclientrect-params/65504/5 "2024-08-15T15:17:32Z")

</div>

Based on my experience, if such things are not done especially (what you said) in the client side. People’s interest in bringing JS ecosystem frameworks is increasing.

And this is exactly the point where I have to say that like js, everyone creating something rather than solving the previous problem. I hope it doesn’t happen like this

---

_[View the full topic](https://forum.elixirforum.com/t/adding-phoenix-liveview-js-function-for-getting-getboundingclientrect-params/65504)._