Screenshots is Shipping in Firefox 56
medium.com
Screenshots is Shipping in Firefox 56
1–5 of 5 posts
Re: Screenshots is Shipping in Firefox 56
#2This is a great feature. I'll freely admit to taking gratuitous screenshots to share things (Cmd-Shift-Ctrl-4 makes it so easy on a Mac); of course, this makes the image impossible to search for later. It would be great to be able to search through the images I lazily take with a good old text search.
If Mozilla keeps it up with features and performance improvements, they'll lure me back from Chrome.
Re: Screenshots is Shipping in Firefox 56
#3Re: Screenshots is Shipping in Firefox 56
#4It's lame that they put that option at the bottom of the contextual menu when you right-click on a page. I'm constantly triggering the screenshot mode when I'm trying to Inspect Element.
Screenshots is implemented as a WebExtension. Unfortunately, the WebExtensions framework in Firefox currently appends items to the bottom of the context menu--so you'll notice this with other WebExtensions, too.
There's a bug open to change this behavior: http://bugzil.la/1325758 . If you'd like to hack on some browser JS, I'd be happy to help get you connected with a bug mentor on the addons team :-)
Re: Screenshots is Shipping in Firefox 56
#5It's lame that they put that option at the bottom of the contextual menu when you right-click on a page. I'm constantly triggering the screenshot mode when I'm trying to Inspect Element.
Yeah, this is a legit concern. Screenshots is implemented as a WebExtension. Unfortunately, the WebExtensions framework in Firefox currently appends items to the bottom of the context menu--so you'll notice this with other WebExtensions, too. There's a bug open to change this behavior: http://bugzil.la/1325758 . If you'd like to hack on some browser JS, I'd be happy to help get you connected with a bug mentor on the…
Some of the use cases for precise placement capabilities seem pretty compelling, but here's hoping for accessible user customization options as a long term solution, perhaps in conjunction with the ability for WebExtension developers to set appropriate default placement, as long as that placement is not below Inspect Element. Inspect Element at the bottom is sacred!