Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by wlesieutre on Saturday July 02, 2016 @03:56PM
(#12023615)
This bookmarklet was well received last time I mentioned it, so I'll link it again: https://alisdair.mcdiarmid.org/kill-sticky-headers/
Finds anything with position:fixed and deletes it. Reload the page to get the elements back if needed.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by ivanca on Saturday July 02, 2016 @11:40PM
(#12024726)
A more sensible solution would be to convert all fixed elements into "position: absolute" ones. That is less prone to cause errors and avoids impeding navigation.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by wlesieutre on Sunday July 03, 2016 @04:25AM
(#12025235)
You'd think so, but I've seen a lot of websites that dump a sticky "social sidebar" on top of the content, and if it's absolutely positioned you can't read the stuff that it's stuck in front of.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by tokensimian on Sunday July 03, 2016 @12:28AM
(#12024819)
You are correct.
However, the sites that do the overkill of a sticky header tend to also have poorly thought out site navigation and user experiences.
Let's say on a normal site, killing any absolute nav would result in a 5%* decrease in UX.
On a site like this, killing any absolute nav might result in a 5% increase in UX.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by 746F7475 on Sunday July 03, 2016 @04:21AM
(#12025229)
But that doesn't work as well, since for example on this page there is JS event tied to scrolling the page that moves the header with you. So you'd have to tie your own anti-move trigger to the same event, which might mean same script won't be universal. If you just remove the header with a script, you can still get to the navigation by refreshing the page.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by ivanca on Sunday July 03, 2016 @04:53AM
(#12025294)
I actually just tried in this page and it works perfectly even before any scrolling has happened by just using "position:absolute !important" in the "position:fixed" elements;
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by stephengillie on Saturday July 02, 2016 @03:49PM
(#12023594)
Try disabling JavaScript. Without that, other than some iframe code up top, everything seems to display correctly on mobile Chrome.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by thesimon on Saturday July 02, 2016 @03:09PM
(#12023491)
Same on Chrome & Safari on Mac, but didn't notice it while reading, only when I read your comment :)
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by alexpetralia on Saturday July 02, 2016 @03:24PM
(#12023533)
Same here, just noticed upon rechecking
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by miahi on Saturday July 02, 2016 @03:12PM
(#12023496)
Exactly the same. I had to open the page again to see that there's a huge header.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by krallja on Saturday July 02, 2016 @05:35PM
(#12023873)
Yes. Firefox Reader View fixed that problem for me.
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by kalleboo on Saturday July 02, 2016 @07:04PM
(#12024112)
Safari Reader Mode worked a treat over here
Re:How I Cracked a Keylogger and Ended Up in Someone's Inbox
by rmsaksida on Saturday July 02, 2016 @06:33PM
(#12024012)
Yep. Had to right click, inspect element, delete the header element. Article is unreadable otherwise.
[0] http://puu.sh/pNYUH/d42d8395fc.jpg