3 ms·
It was fine for me, although the images were much delayed on loading, so there is some javascript acting there. Are you using noscript?
by ars 12y ago
It was fine for me, although the images were much delayed on loading, so there is some javascript acting there. Are you using noscript?
- ggchappell 12y ago> Are you using noscript? No. The only thing I explicitly block is flash. (Also, I don't recall having a problem like this before.)
- ars 12y agoWhat url do you have for the bad images? A good image url is: http://ichef.bbci.co.uk/wwfeatures/1280_720/images/live/p0/27/l1/p027l1df.jpg http://ichef.bbci.co.uk/wwfeatures/1280_720/images/live/p0/2...
- ggchappell 12y agoI get this: https://ichef.bbc.co.uk/wwfeatures/304_171/images/live/p0/27/l1/p027l1df.jpg https://ichef.bbc.co.uk/wwfeatures/304_171/images/live/p0/27... Probably this isn't worth a whole lot of work; I guess it thinks I'm on a phone (I'm not).
- ars 12y agoWhat's your user agent? Maybe you set it funny and forgot. http://www.useragentstring.com/ http://www.useragentstring.com/
- Pwntastic 12y agoAre you using ghostery? I was seeing something similar until I allowed Brightcove to load through ghostery
- ggchappell 12y agoNot using ghostery. > I was seeing something similar .... Well, then it isn't just me. Something about the BBC site's resolution handling is borked, I guess.