Closed Bug 1075243 Opened 10 years ago Closed 5 years ago

breakdown: mechanism for capturing tab thumbnails at desired size, and using those for newtab

Categories

(Firefox :: New Tab Page, defect)

defect
Not set
normal
Points:
3

Tracking

()

RESOLVED WONTFIX

People

(Reporter: Gavin, Unassigned)

References

Details

The goal is to fix bug 1059559.

I brainstormed an approach:
- teach both thumbnailers (foreground and background) to optionally capture newtab-sized thumbnails (which are now a fixed size)
- for the background case, have the newtab specify that it wants thumbnails of that size when the newtab requests a thumbnail from the background service
- for the foreground case, have the foreground thumbnailing code check whether the current page is a page that we display on newtab, and if so capture a newtab-sized thumbnail
- adjust the moz-page-thumb protocol handler to allow specifying that you want specifically sized thumbnail, and have the newtab page use that

We should break that approach down into individual work items and see whether it's feasible, and scope out the work.
Flags: qe-verify-
Flags: firefox-backlog+
Points: --- → 3
Iteration: --- → 35.3
Some background as far as I understand:

1. The (hidden) browser window which is used to capture these thumbnails is ~1000px wide (maybe 1024x768?). This might be doubled on retina displays.

2. The captured image is then immediately scaled to 1/3 screen width x 1/3 screen height, and stored this way. On a 1920x1080 screen that's 640x360.

3. The current consumers for this scaled image are:
- newtab page
- ctrl-tab (when browser.ctrlTab.previews = true)
- Panorama

4. The newtab page then renders this image at 290x180 (probably doubled for retinas). Not sure how the other consumers render it, but I think the ctrl-tab one renders it bigger than that.


When we experimented with capture (re)size of 290x180, it turned out that scaling directly from the window size (~1000px) to the newtab thumb size (290px) without the intermediate step if 1/3 screen size, the scaling quality was unsatisfactory.

It was noticeable e.g. on Apple's pages texts where they use fonts with relatively thin lines, which were not fun to look at at the newtab page, but looked fine with the 1/3 screen intermediate scaling.

We're still not sure if that's a bug or not, but this is something we'd have to deal with if we scale directly from the window size to the small newtab thumbs size.
Iteration: 35.3 → 36.1
Just spoke to Tim, we're going to drop this bug for now.
Assignee: ttaubert → nobody
Iteration: 36.1 → ---
Flags: needinfo?(mmucci)
Removed from IT 36.1
Status: ASSIGNED → NEW
Flags: needinfo?(mmucci)
Does this mean the newtab page will keep resizing the thumbnails for the foreseeable future?
Flags: needinfo?(ttaubert)
For this iteration we're going to concentrate on investigating the perf problems with the new preloader and try to get some feedback for the "delay showing images" patch. We will re-evaluate next iteration based on the results.
Flags: needinfo?(ttaubert)

Hello!

This bug has been closed due to inactivity and/or the potential for this bug to no longer be an issue with the new Discovery Stream-powered New Tab experience.

Please help us triage by reopening if this issue still persists and should be addressed.

Thanks!

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.