Recreate screenhots and screencasts in new Firefox design

Question

Recreate screenhots and screencasts in new Firefox design

rugk opened this issue 3 years ago · 15 comments

The screenshots still follow the old Photon (tab) design, which of course does not

The new design with floating tabs looks very much different. So all images and screencasts need to be re-made.

If anyone wants to contribute, this is a very easy task! You see all files in the assets/screencasts and assets/screenshots directories. You just need to look at them and do/screenshot (exactly) the same in a new modern Firefox (stable or even Firefox Developer Edition is enough), replace all files and create and submit a Pull Request.

Also mind to keep the pixel sizes (width/height) of the GIFs/images approximately the same, as they were optimized for the display on addons.mozilla.org (AMO) etc.

Answer 1 · 2021-08-26T20:36:26.000Z

Sounds pretty straightforward! I can tackle it if you want to go ahead and assign me. I can knock it out some time today or tomorrow.

Answer 2 · 2021-08-26T21:39:00.000Z

Thanks a lot for taking this on! 😃 Feel free to send a PR if you've done it.

Answer 3 · 2021-08-27T18:36:45.000Z

Thanks!

How exact did you want the new screenshots to match the old ones @rugk? I can get the dimensions to match easily but do you also want the exact same Firefox themeing, etc.?

Answer 4 · 2021-08-27T23:35:11.000Z

It does not have to be exactly the same (pixel size), but the same general theme e.g. would be quite nice.
The OS does not matter.

Answer 5 · 2021-08-28T19:49:47.000Z

A little busier IRL than I thought I'd be, sorry!

The English screenshots are done, just need to do the screencasts and screenshot the German settings.

Answer 6 · 2021-08-28T21:22:11.000Z

Oh sure, thanks a lot! Did not even remember I screenshott'ed the German settings separately, that is nice.

Answer 7 · 2021-09-02T21:13:04.000Z

Alright, sorry for the delay!

Pull request #271 has the new screenshots and screencaps.

Answer 8 · 2021-09-03T19:03:47.000Z

Thanks a lot, no problem. Take the time you need. 🙂

Answer 9 · 2022-09-17T05:39:30.000Z

Hi there. Is this task still available? I would like to offer my assistance if possible

Answer 10 · 2022-09-17T11:42:21.000Z

Sure it is, so I assign it to you @Tch4lla then. 🙂

Thanks for your work already. 🙂

Answer 11 · 2022-09-19T12:31:21.000Z

Is this issue resolved? I want to contribute in it.

Answer 12 · 2022-09-19T21:25:44.000Z

I have already submitted my pull request for this issue, and am currently waiting on confirmation if there are any changes or tweaks that need to be made.

Answer 13 · 2022-10-19T13:19:43.000Z

Indeed, #284 is the PR to fix these, Sorry for the delay, I was busy and missed the notifications.

I assume, if help is needed, @RohitRajvaidya5 you can jump in and help here. Feel free to test or review the existing PR, BTW.

Answer 14 · 2022-10-24T01:29:55.000Z

Ahh, thank you for getting back to me You have left some great advice and I will try to implement those this week.

…

On Wed, Oct 19, 2022 at 10:19 PM rugk ***@***.***> wrote: Indeed, #284 <#284> is the PR to fix these, Sorry for the delay, I was busy and missed the notifications. I assume, if help is needed, @RohitRajvaidya5 <https://github.com/RohitRajvaidya5> you can jump in and help here. Feel free to test or review the existing PR, BTW. — Reply to this email directly, view it on GitHub <#268 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXYA7KYGKAK26SZYOPLDT4DWD7YPXANCNFSM5CISSKIA> . You are receiving this because you were assigned.Message ID: ***@***.***>

Answer 15 · 2022-10-30T05:20:12.000Z

I have made those adjustments and have submitted and updated pull request. I hope that it is not too much work to merge