Earlier quoted context omitted.
What do you call that giant banner that drops down on Medium (and other sites) every time I accidentally scroll up a pixel? I hate that thing.
I call it the nav teabag.
No, I Don’t Want to Subscribe to Your Newsletter
211–220 of 221 posts
Re: No, I Don’t Want to Subscribe to Your Newsletter
#212Earlier quoted context omitted.
How would you go about detecting when a user is about to leave your site? Other than responding to a click on an external link? The two ways I typically leave a site are a) typing a URL into the address bar and b) closing a tab.
Scrolling up seems pretty popular. Why wouldn't you want a half-page menu telling you what to read next when you scroll up to check something?
Or at least, that's me. If I want to go back to navigation, I hit the Home key (the vast majority of systems do have one or two of them...). If I'm scrolling up, it's to read.
Re: No, I Don’t Want to Subscribe to Your Newsletter
#213Re: No, I Don’t Want to Subscribe to Your Newsletter
#214If you don't want to see my pop up asking you to subscribe to my newsletter after you've scrolled through half the article I wrote (that you have shown to be interested) then you are free to leave and not come back. Deal.
On the other hand, if there's a non-popup at the end of post that asks for my email address, and if I liked the content and think more would be useful ... I'll provide it.
Re: No, I Don’t Want to Subscribe to Your Newsletter
#215Re: No, I Don’t Want to Subscribe to Your Newsletter
#216Yes, I want to subscribe to your newsletter! Automatically with a browser plugin, with an address that will even accept your mails. Unfortunately no human will read them in the end, but I'm sure your metrics will be great. I might even accept a cookie so you know I'm already subscribed to your great newsletter. Now if everybody were to do that...
Re: No, I Don’t Want to Subscribe to Your Newsletter
#217Earlier quoted context omitted.
Do you know of a way, say in the JavaScript console (I'm guessing?), to reset scroll behaviors? I'm not clever enough with JS or CSS to have figured it out. Deleting the modal using the inspector is what I do but I can't get around the scrolling...
This will solve the problem for you on most sites: document.getElementsByTagName('html')[0].style.overflow = "scroll"; The css property you're looking for is "overflow," usually on the body or html tag.
It may also be necessary to remove event listeners.
Re: No, I Don’t Want to Subscribe to Your Newsletter
#218Re: No, I Don’t Want to Subscribe to Your Newsletter
#219Earlier quoted context omitted.
Consensual, transparent censorship. Interesting.
Really not that different than kill files, something comment threads still desperately need. I realize I'm well off the curve here, but I'd still love a browser killfile plug in with: - fine-grained cookie management by name/secure status/path - Make every cookie a session cookie in a given domain - "Cookie pipes": I'd like the ability to execute scripts on cookie value changes, optionally returning a new value - Jav…
Opera used to have this ;'-( before they fired the entire Presto (browser engine) team and switched to webkit/chrome.
I've been giving the "modern" Opera a test run for the past week and while it's still way snappier by miles (compared to firefox and chrome, on a slow laptop) but it still misses so many features I used to depend on in the 2000s.
Yes you can get add-ons for almost all of the functionality, but you'll grind firefox or chrome to a halt before you even get close the the functionality of the old Opera that just came with all that stuff, batteries included.
(before accusations of bloat: installer/executable size was tiny, I seem to remember below 1MB for medium-old versions)
Re: No, I Don’t Want to Subscribe to Your Newsletter
#220IMO it doesn't worth the time to discuss appropriate and inappropriate uses of JavaScript. It's way simpler to disable it entirely. I use two browsers: Firefox with "YesScript" extension which keeps the black list of sites where JS is disabled: see a popup? laggy scrolling? sticky headers? Bam! hit the button and you won't see it again. For work, where web applications like Google suite matter, I use Chrome. Some tim…
> position:fixed (auto-replace to position:static) I've gotten pretty good results from a bookmarklet that converts `position: fixed` elements to `display: none`.
javascript:for (let e of document.querySelectorAll('*')) if (/fixed|sticky/.test(getComputedStyle(e).position)) e.style.position = 'static';
I use it so many times a day it's not even funny (it's in my bookmarks bar, keyed to ctrl-2). I think it removes (or obscures) an element that I wanted to see in hindsight, way less than 1% of the time. It would be nice if I could just tell the browser to just ignore the `fixed` or `sticky` position properties entirely.