The frontend uses prefs to determine max displayport width/height. For sites that are either naturally skinny or set a skinny <meta viewport> (resp. wide), however, we vastly underutilize available displayport area by clipping to max-width/max-height. It would be better instead to calculate a maximum displayport *area*, then optimize displayport width/height to fill that area. I would bet that by doing this we would be able to fully cache many popular mobile sites that use <meta viewport>. (We can make this a subset of optimizations for bug 624451, but this seems simpler and higher-value to implement, so I personally would do this first.) This is made more complicated by GL texture limits, but I take this bug with CPU compositing before GL compositing without this bug. We can look into texture-tiling or whatever when the need arises. This is going to make bug 593243 more noticeable. Won't set dep yet, can let experience tell.

Good idea. > This is going to make bug 593243 more noticeable. Won't set dep yet, can let > experience tell. Since we are now calling scrollTo after a pan is finished, this isn't a big deal IMO.

(In reply to comment #1) > > This is going to make bug 593243 more noticeable. Won't set dep yet, can let > > experience tell. > > Since we are now calling scrollTo after a pan is finished, this isn't a big > deal IMO. I don't know the details there but I'm happy to let experience tell.

This change was made in bug 624451.