# HTML for floating button - here you go!

**URL:** <https://community.glideapps.com/t/html-for-floating-button-here-you-go/18321>\
**Category:** Community Resources\
**Created:** [November 12, 2020, 5:55pm UTC](https://community.glideapps.com/t/html-for-floating-button-here-you-go/18321 "2020-11-12T17:55:38Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![panda](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/panda/32/49438_2.png) [@panda](https://community.glideapps.com/u/panda)\
**Post date:** [October 27, 2022, 8:04pm UTC](https://community.glideapps.com/t/html-for-floating-button-here-you-go/18321/21 "2022-10-27T20:04:54Z")

</div>

You normally don’t have to include “\< pre \>\< span \>\< style \>” tags when targeting a class and changing that CSS, so wondering, why that needs to be added.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [October 28, 2022, 1:00am UTC](https://community.glideapps.com/t/html-for-floating-button-here-you-go/18321/22 "2022-10-28T01:00:01Z")

</div>

It’s a way figured out by @Robert_Petitto . I’m not sure technically why we need that, but I think it’s the only way our code would be seen as CSS to the system, otherwise it will be treated as normal rich text.

[Previous page](https://community.glideapps.com/t/html-for-floating-button-here-you-go/18321.md?page=1)
