Here's how I would improve this: The lightbox that opens up asks, "Looking for the GitHub logo?" But it doesn't let you answer no. It just presumes that your answer is yes, and supplies you with what it thinks you actually want (or, more cynically, what it wants you to want). I would suggest adding a "No thanks -- just let me right-click" link at the bottom. That link would close the lightbox and prevent it from reop…
This answer sent shivers down my spine.
Try right clicking GitHub's logo
101–110 of 148 posts
Re: Try right clicking GitHub's logo
#102Here's how I would improve this: The lightbox that opens up asks, "Looking for the GitHub logo?" But it doesn't let you answer no. It just presumes that your answer is yes, and supplies you with what it thinks you actually want (or, more cynically, what it wants you to want). I would suggest adding a "No thanks -- just let me right-click" link at the bottom. That link would close the lightbox and prevent it from reop…
Re: Try right clicking GitHub's logo
#103Earlier quoted context omitted.
and give me an API to query if a user likes the right click override setting off and on. "Gravatar for right click settings."
Also A/B test the pop-over dialog to see what works best.
Re: Try right clicking GitHub's logo
#104Earlier quoted context omitted.
You must be a program manager - you have taken a simple and easy solution and added a ton of complexity for a problem 1% or less of people will encounter.
Am I really in a <1% minority of people who right click site logos to open the main page in a new tab and start a separate browsing path?
I think there's a small market for a browser (or browser plugin) that's all about client control. Querying mouse position, hijacking keypresses and showing popup windows and modal dialogs should be activated with a "This site tried to... Allow/Deny".
NoScript gets part of the way there, but I think you could go even further. Pages should display as soon as the HTML starts downloading, before CSS is loaded, before JS is all there, whatever. I don't care if this causes the page to jump a few times, or if it breaks a few scripts because it's not standards compliant, I just want to read my content on a slow connection.
I probably want to disable webfonts. They're a vanity thing, mostly, and the more I consider it the more I think I should be picking the fonts I read.
Maybe you could go even further - for specific sites with really atrocious interfaces you could have custom-written interfaces that almost completely remodel them (a'la Readability, I guess). I'm sure it would annoy web developers to have their pages render "incorrectly" on your screen, but screw them. My browser, my rules.
Re: Try right clicking GitHub's logo
#105Re: Try right clicking GitHub's logo
#106Re: Try right clicking GitHub's logo
#107Earlier quoted context omitted.
You must be a program manager - you have taken a simple and easy solution and added a ton of complexity for a problem 1% or less of people will encounter.
Am I really in a <1% minority of people who right click site logos to open the main page in a new tab and start a separate browsing path?
Re: Try right clicking GitHub's logo
#108Re: Try right clicking GitHub's logo
#109Earlier quoted context omitted.
Requires two hands, but I often find it easier to control-click on links to open in a new tab, and that still works in this case.
I open new tabs with middle click (scroll wheel click). That works too. It also works for closing tabs.
Re: Try right clicking GitHub's logo
#110Earlier quoted context omitted.
You must be a program manager - you have taken a simple and easy solution and added a ton of complexity for a problem 1% or less of people will encounter.
Am I really in a <1% minority of people who right click site logos to open the main page in a new tab and start a separate browsing path?