Michał

@DantSu ?

And related to the above, we should probably reconsider this rule: ``` [aria-busy="true"]:not(input, select, textarea, html) { white-space: nowrap; } ``` Which causes overflow issues when we have an overflow...

@MatteoGabriele the link does work. Example of it working: https://pagespeed.web.dev/analysis/https-developers-google-com-analytics-devguides-collection-ga4-set-up-ecommerce/tigql381sd?form_factor=mobile When you get it to work, you'll see the example code provided by Google.

@MatteoGabriele that's weird - it's a public resource from Google. Did you try to CURL/WGET it, from a different browser, or just on a different device like your phone? Anyway...

@MatteoGabriele I have opened the relevant pull request https://github.com/MatteoGabriele/vue-gtag/pull/585. Additional details, links, and discussion points are there too :)!

@MatteoGabriele have you given up on this project?

@ricardasjak hmm. There does seem to be some sort of leak on this page. I am seeing a continuous increase in listeners and JS heap.

> Have you tried manually instantiating `\Codewithkyrian\Transformers\Utils\InferenceSession` and calling the `run` method? I can't recall - but to be clear, are you asking or are you saying it can be...

Note my suggested fix fails in the case of having another dropdown as a direct child of details (rather than in a `ul` as I've shown in the original issue):...

There is another problem in rendering that causes any details elements as children of a dropdown to also render as a dropdown. This is due to this line `details.dropdown[open] summary::before`...