#Weird window for opening Emote menu

1 messages · Page 1 of 1 (latest)

merry violet
#

I tried opening the emote window and the 3rd image is what it looked like, I believe this might be due to the Firefox version I am using (Version 116.0.3 (64-bit))
What I did

  • click the 7TV button in the chatbox
    This caused the 3rd image to happen
  • clicked the 7TV button after a few seconds
    Caused the 2nd image to happen I think thats the normal twitch emote box
  • clicked the 7TV button after a minute
    This is the normal 7TV emote box right?
nocturne rain
#

its a weird stylesheet caching issue that should be impossible but still happens

#

its a firefox bug

#

it should always resolve after a restart

merry violet
#

what browser do you recommend?

nocturne rain
#

I mean I use firefox myself

#

i don't typically have this happen, it usually only happens after an extension update

#

but there are other reasons it can happen too

#

basically it happens if the cached versions of two of the loaded files are different

merry violet
#

I see, thanks for the quick response

nocturne rain
#

the ui tries to render something expecting the old hash numbers

#

while the styles for those hash's arent actually loaded because a different one has been cached even though its not supposed to be

#

@merry violet also make sure that you're using the current version of the nightly or stable builds for firefox

#

if you previously installed it from the addons.mozilla page

#

uninstall and reinstall from 7tv.app

#

the ones that were on amo were outdated and we cant publish new ones

merry violet
#

I installed it from the 7TV website

#

So its probably a cache issue

nocturne rain
#

yeah its also possible that this happens if the stylesheet just cant be loaded in general

#

sometimes the extension pulls down updated versions from the remote site if the current build you're using is out of date

#

which may allow for a situation where that request fails and then the extension is left with no stylesheets

#

if there was a temporary connectivity issue

#

in either of the cases a restart of firefox should fix