You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.
Currently the screenshots homepage reflects pre-photon UI for both firefox and Screenshots.
We need to do the following:
If the user is on <= 56 or in a non-ff browser, the UI should remain the same.
If the user is on 57 +, we should reveal the currently hidden Full page capture section
If the user is on 57 + we should swap the Get Started section as follows:
Title remains the same
Sentence changes to: Select the Screenshots icon from the page actions menu in the address bar, and the Screenshots menu will appear on top of your browser window.
Was looking for the screenshots icon (using it since it was in test pilot) and couldn't find it anymore, also not as add-on. When checking the about:newtab on-boarding I landed the screenshots homepage stating the icon should be there. I already checked bugzilla for reports of missing screenshots add-on.
Eventually found this bug ... and the tool ;)
I thought something is wrong, everytime I do a new profile cleanup, it doesn't show up in the Customize section. Then it takes me quite some time to find this bug report, so that's where the Screenshot button now at, oh well...
- For 57+, include the full screen / save visible step in the tour, for
four steps overall. Also change the Get Started text and image to
refer to a page action, not a toolbar button.
- For 56- and non-FF browsers, show the three step tour and refer to the
toolbar button.
- Add some trivial model unit tests, to get that ball rolling.
Currently the screenshots homepage reflects pre-photon UI for both firefox and Screenshots.
We need to do the following:
Get Started
section as follows:Once 57 formally ships in release, we should change the show/hide logic for here so that non-FF users and 57 users see the same thing.
The text was updated successfully, but these errors were encountered: