META: blue screen of death

Submitted by snarling wolverine on
I’ve noticed that for some threads, you can initially access them but later they just get a blank blue screen. (I’m not talking about threads that have been locked.) This is currently the case for me for the “Some Perspective on a Few Things” thread. Do other people experience this? I’m assuming it’s just a glitch?

jmblue

October 29th, 2017 at 7:18 PM ^

I don’t buy those rankings. Our hamster recruiting under the previous regime was subpar. Of course, other schools were offering them celery under the table and flashy new water bottles. Facilities need to be upgraded if we want to compete.

killerseafood3

October 29th, 2017 at 6:16 PM ^

Same, on both mobile and browser. Maybe somebody embedded something that is causing it to go stupid for some configurations. Too bad, that’s a thread I was enjoying following.

TruBluMich

October 29th, 2017 at 6:22 PM ^

It's because people can insert a new body tag via the comments.  Giving that new body tag a style of "style="position: absolute; top: 12px; width: 1px; height: 1px; overflow: hidden; left: -1000px;" - it makes the body of the document 1 px x 1px tall and 12px off the top of the page and -1000 pixels off the left side, and hides the scrollbars. Because it is farther down and inline the new style overrides the sites style for the body tag. I informed them of this a few weeks ago and the rememdy was to shut off the comments.
 
 The user responsible in the thread "Some Perspective on a Few Thngs" is Minus The Houma. It appears he copied and pasted the code, accidentaly, from another site to display stats.

TruBluMich

October 29th, 2017 at 6:31 PM ^

If the mods can't get to the post to delete it.  They can place this in the CSS sheet for the site and it should enable them to load the page and prevent it in the future.  A filter is by far the way to fix it, that way nobody can misuse it.

body {

position: relative !important;
top: 0px !important;
width: 100% !important;
height: 100% !important;
overflow: scroll !important;
left: 0px !important;

}

LSAClassOf2000

October 29th, 2017 at 6:27 PM ^

Busted HTML. It's a bitch to find it sometimes too.

Like someone said above, it's a bad tag or some other line which was left open or incomplete somehow. 

It would be funny - for me, not you - to have deleted threads display the blue screen of death from a page fault or some stop error. 

M-Dog

October 29th, 2017 at 7:39 PM ^

i thought it was a retaliatory strike by Brian, thus escalating the great Twitter Conflict of 2017.

All I am saying is give Peters a chance.