Hotjar support available in Lit 2.x? #2265
-
|
My team (Carbon for IBM.com Web Components / Carbon Web Components) is currently on lit-element/lit-html, and currently roadmapping our upgrade to Lit 2.x along with other major version upgrade tasks on our plate. One of the issues we are noticing is that Hotjar (https://help.hotjar.com/hc/en-us/articles/115012499507-Platforms-and-Frameworks-not-Compatible-with-Hotjar) doesn't appear to work (CSS isn't rendering in heatmap screenshots) and is a tool that our data analyst teams use extensively for analyzing our website traffic. Anyone know if Hotjar works with Lit 2.x? Or is there something we can do on our end that can get it working on existing lit-element/lit-html? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
The long-term solution is for Hotjar to implement support for constructable stylesheets. Meanwhile, you can force Lit not to use constructable stylesheets by including a script tag like this in the page before loading Lit:
It's kind of gross, but it means we don't need to add configuration complexity to the Lit API and it does exactly what you need to do to make Hotjar work. |
Beta Was this translation helpful? Give feedback.
-
|
@graynorton would it be an option to reconsider #1811 and add a flag to avoid patching browser API manually? |
Beta Was this translation helpful? Give feedback.
-
|
Oh, thanks @graynorton! This other section confused me:
It must be an older mention. Glad to hear that Hotjar already supports Shadow DOM! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the response, I might actually do some testing with removing adopted stylesheets to see if this is a workaround for us for now. And as mentioned, I have already reached out to the Hotjar team to see how quickly they can adopt adopted stylesheets. |
Beta Was this translation helpful? Give feedback.
-
|
@web-padawan We'd prefer to avoid adding Lit API surface and code complexity for this unless it proves absolutely necessary. For the use case described in this discussion, it seems like it would be a problem for anyone to use constructable stylesheets on the page, not just Lit—so disabling globally actually seems like a more suitable fix. I think what it would take for us to reconsider #1811 would be for someone to come up with a realistic and important use case where it was necessary to disable constructable stylesheets for all Lit elements, but not for anything else on the page. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the answer. I don't have a strong opinion regarding Lit API shape. You can also close #1811 as won't fix. |
Beta Was this translation helpful? Give feedback.
The long-term solution is for Hotjar to implement support for constructable stylesheets.
Meanwhile, you can force Lit not to use constructable stylesheets by including a script tag like this in the page before loading Lit:
<script>delete Document.prototype['adoptedStyleSheets'];</script>It's kind of gross, but it means we don't need to add configuration complexity to the Lit API and it does exactly what you need to do to make Hotjar work.