InformAction Forums

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0a1
Built from http://hg.mozilla.org/mozilla-central/rev/7e4c2abb9fc9
Noscript 2.4.4rc2

1) Visit http://www.halifax.co.uk
2) Allow *.halifax.co.uk but disallow webtrends.com
3) Navigate to http://www.halifax.co.uk again

Expected:
Page loads in a similar time compared to "allow scripts globally" or allowing both *.halifax.co.uk *and* webtrends.com

Actual:
Blue/grey page background for several seconds before the main page content renders.

--

This may just end up being the bugzilla.mozilla.org equivalent of Tech Evangelism::*, since I'm sure they are doing something stupid on pageload with webtrends - but thought I'd file this in case the webtrends tracking nonsense can be stubbed out, similar to Google Analytics is at present (if I've remembered correctly).

Thanks!

I just tested this mate and it seems that it has nothing to do with NS. It works fine and as expected for me. I am guessing it might be something with the particular build and something on Mozilla's side that is causing this but I'll be honest, I do not have that particular build, just the latest stable, so guessing it might be a transitional issue or something introduced or existing in that particular build. Hopefully Giorgio will have more on it, if anything more.

I can recreate this still on Nightly and latest dev NS.

Can reproduce on latest aurora and beta.
Seems like the content is there just somewhat invisible (page size does not change when it becomes visible and you can do "select all" before it's here).

/edit: Humm… "page-ready.js"? Also I wonder what the following is for:

Sorry, I couldn't reproduce because I don't get any webtrends.com script (maybe it's a regional thing?)

I could not reproduce this as stated before but given there was two more posts about it, I asked Giorgio to look into it and you have his reply here. So I am not sure how we can go about trying to hammer this out. To test the regional assumption, I used a UK server AND proxy to access the resources listed and I had none of the issues described. Now that doesn't mean its not a regional thing but I can pretty safely say that its not that, its gotta be something else playing into this. Just say for what its worth.

Thank you for trying anyway

edmorley wrote:Thank you for trying anyway

You are most welcome, that's what we are here for.

1) Visit http://www.halifax.co.uk
2) Allow *.halifax.co.uk but disallow webtrends.com
3) Navigate to http://www.halifax.co.uk again

Expected:
Page loads in a similar time compared to "allow scripts globally" or allowing both *.halifax.co.uk *and* webtrends.com

Actual:
Blue/grey page background for several seconds before the main page content renders.

Confirmed.

And once you have allowed both *.halifax.co.uk *and* webtrends.com, if you then Forbid webtrends.com, you see the same again.

Or even ...

1) Visit http://www.halifax.co.uk
-> with neither *.halifax.co.uk nor webtrends.com allowed (page loads fine)
2) Allow *.halifax.co.uk

Blue/grey page background for several seconds before the main page content renders.


Note that webtrends.com does not become viewable until after you have already allowed *.halifax.co.uk.

There are a number of external.js, like http://www.halifax.co.uk/common/script/webtrends_hfx.js but their source domain is still halifax.co.uk.

It could also be that they made their code dependent on something that is linked to a webtrend script and so when its disabled and you reload, it takes a bit for it to try and do some parsing before giving up and loading, that may be just by design on the website, which would definitely not make it a NS issue.