Hacker News Reader

Comment by 51Cards | Hacker News Reader

>The ‘Take a Screenshot’ feature was removed from the Page Actions menu in the url bar.

Odd, this is the only place I accessed it from. Not a big deal as it's still on the context menu and also can be added as a tool bar item but I am curious the rationalization behind this change. That seemed like a great place to have it to me.

View on HN

When I first tried to use it, I knew of the feature but couldn't find it. They probably have metrics on it being underutilized so they want to bring it forward a bit or so.

But I think the whole "page actions" button is too hidden. I think screenshot belongs there, and the issue is that most people don't know without being told that "page actions" is something that even exists.

It's great btw to take screenshot of loooong web pages smoothly.

> the issue is that most people don't know without being told that "page actions" is something that even exists.

I'm a daily Firefox user for quite a while now... thanks for telling me this exists! Never really looked into what those 3 dots were.

(That being said, I always right click to trigger the screenshot option from the context menu.)

the right click screenshot is one of the most useful features i didn't know i need; it's super convenient to not have to precisely draw the rectangle to share a meme or report a bug.

Choosing to screenshot the entire page seems to be cropping off most of the right side on every site I've tried so far. Is that a known bug? It would be really useful otherwise.

I typically use Ctrl+Shift+S for this

I likely would as well if I remembered it. I have always had a problem recalling key combinations across all the applications I use which is why I rely on context menus and tool bars heavily. I've called out VSCode on this a few times as well as it is a memorization fest to work efficiently in there without proper toolbars. It's not just this but I have memory issues in general which have only gotten worse as I've aged. Easy discoverability / access in UI design is a big focus for me.

when I discover a new key-combo I write it on a postit at the bottom of my monitor, lives there for a while until it sticks in my brain.

In VSCode, use Ctrl+Shift+P to bring out the command palette and type in your wish. The corresponding shortcut is also displayed.

Yep, but I find it to be a really poor paradigm for efficient work if you don't remember them. Having to search the command palette is much slower than being able to set up a toolbar of often used functions. Don't get me wrong, the command palette is great to have but if you can't memorize all those functions then it's a really poor replacement.

For efficiency Key combo > toolbar > command palette. I just hate to be forced into #3 because #2 doesn't exist. (not to mention that the developers make crazy arguments in the forums about why they refuse to impliment it... but that's all off topic)

If you use Windows, newer versions (v1809 and newer) have win+shift+s as a neat region-select screenshot tool that sends the image to your clipboard.

There is still a "Take Screenshot" menu item in the context menu when you right-click on a web page.

Unless the context menu is not available, that is.

When is the context menu not be available? If the website is overriding the right click action, keep shift pressed while clicking to gain back control.

There are several pages on AWS that do not show it. For example, most CloudWatch pages.

I think it has to do with iframes.

You can shift+right click if a page (like the ones on AWS) block right clicks.

You can shift+right click normally too, even when a page doesn't block right click.

It's not about blocking or hijacking right-clicks. The menu option simply isn't there when the right-click happens in an iframe.

Google pays Mozilla to make Firefox worse to use. An bring more people to Chrome.

Reply on news.ycombinator.com