[RESOLVED] Page loading/split-second scripts?

[Guz]

Hello, I noticed a few issues with scripts loading for a split second when active on a page, such as if I'm on Twitter and the media server is blocked I'll see the screencap for the video (and the play button) pop up for a brief moment before it reverts to the "Video cannot be played" placeholder image.

I was just a bit concerned as to if this means that scripts are loading for that split second, or if it's just something innocuous that I don't need to be concerned about like just the way certain sites detect noscript.

The best place I can suggest to check this is at http://www.hotukdeals.com/ with everything blocked. When I first go to the site, or refresh the page, I see this log-in page pop up for a split second -> http://i.imgur.com/xo5Xbfc.png before disappearing.

Not sure if it was in fact always like this and I didn't notice, or if there's something buggy on my end.

Thanks!

[barbaz]

Not sure if that's related to NoScript. Could you please post your full list of extensions?

[Guz]

The only things I'm using are Noscript and Adblock Plus.

Running 50.0.2 with e10s enabled.

[barbaz]

What happens there without ABP?

[Guz]

Seems to be the same. Still loading the log-in page for a split second on each refresh.

[barbaz]

Thanks for checking.

This type of thing won't be result of "detecting NoScript". I've seen sites that detect adblock and such, and this is just not how they behave in response.

Furthermore, you say you have all scripts blocked. Detailed blocking detection, such as determining the cause of the blocking, pretty much requires active content.

You can thus conclude that either NoScript itself is making the split-second behaviors, or it's simply the site loading gradually.

___________

In the case of twitter, it sounds like you are literally watching NoScript block the video. No, the video never loaded - only its poster image did.

In the case of hotukdeals, that "pop-up" is loading before the CSS that styles it. And that CSS contains a transition on the "opacity" property. What you are seeing is just the result of that CSS loading.

No need for concern.

[Guz]

Ahh ok. I had a feeling maybe it was something like that, but just wanted to be sure there was nothing messed up on my system.

Thanks for the reply, interesting how that works.

[barbaz]

You're welcome.