On Tue, Jun 18, 2013 at 8:00 AM, Nicolas Silva <nical.si...@gmail.com> wrote: > I feel somewhat uneasy about the idea that thumbnails generate more network > traffic. It would be great to at least throttle that when connectivity is > bad, or when the the user's data plan bill could suffer from it (not sure > how to detect/address something like that). If nothing else, users should > be able to disable this feature.
If we design it properly this shouldn't be a huge issue (and users disabling the feature probably won't be necessary). This isn't something we'd provide UI for, certainly. > Also it's worth noting that thumbnails also have the problem of when it > should be taken. As soon as web pages become applications rather than > simple documents, we tend to screenshot before most of the content is on > the screen. Maybe it's worth thinking about how potential solutions to both > problems interact. I think this is largely a separate problem - when to screenshot vs. how to do it seem mostly unrelated. Do you have any examples of where the current thumbnail code fails to capture a "good" thumbnail? I think it it just uses a hard-coded delay after load, and as far as I know this hasn't really been a problem in practice. B2G's requirements are somewhat different given the way their screenshots are used (as a perceived performance optimization rather than for thumbnails). Gavin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
