1243166 - Experiment with capturing full length of webpage instead of "what's on-screen" when a user (hardware) screenshots in Fennec

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

If a user screenshots in Fennec, they currently press the buttons > go to photo gallery > view series of screenshots.

What if we could capture the entire webpage (like page shot) and still just saved it in their photo gallery? 

No new UI/UX necessary, they simply see a longer image in their screenshots folder.

Comment 1

[Richard Newman [:rnewman]]

If you really do mean "instead of" -- careful. Don't break my "save this particular tumblr post" or "screenshot this particular part of the map" flow; users will pinch-to-zoom or scroll to what they want to save, particularly on infinite-scroll sites!

Maybe wait for the regular screenshot to have occurred then show a snackbar offering to save the whole page?

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

Yes, be aware of comment #1, especially since we can not be notified of the screenshot hardware buttons being pressed. We can only be notified when an image appears in the "Screenshots" album. So the regular screenshot image has to be created.

We could then replace that image with another, but comment #1

Comment 3

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

(In reply to Richard Newman [:rnewman] from comment #1)
> If you really do mean "instead of" -- careful. Don't break my "save this
> particular tumblr post" or "screenshot this particular part of the map"
> flow; users will pinch-to-zoom or scroll to what they want to save,
> particularly on infinite-scroll sites!

That's fair I think.

In the Tumblr example though, wouldn't we only do the post that's loaded? the infinite scroll shouldn't trigger the next batch until the user has hit the bottom of the page... But a fair point in it's own right for sure.

Maps is a particularly good example here - we should definitely be aware of this nuance.

> Maybe wait for the regular screenshot to have occurred then show a snackbar
> offering to save the whole page?

We could. Offering to create an additional one (instead of replacing that image with another) seems okay to me.

(In reply to Mark Finkle (:mfinkle) from comment #2)
> Yes, be aware of comment #1, especially since we can not be notified of the
> screenshot hardware buttons being pressed. We can only be notified when an
> image appears in the "Screenshots" album. So the regular screenshot image
> has to be created.

Seems like a great way to take care of the nuance. We could split ours into it's own Photos/gallery folder even?

> We could then replace that image with another, but comment #1

Yeah, I think creating a dupe is best. Replacing does seem aggressive. 

I think this experiment is very promising considering what we've learned from UR about not teaching the user something new, or making them change the way they're doing things.

Comment 4

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.