Mobile/Layers: Difference between revisions

Jump to navigation Jump to search
Line 8: Line 8:


=== 2.0 b1 TODO ===
=== 2.0 b1 TODO ===
* '''(cjones)''' sort OOMing that's ''still'' occurring
* {{bug|585799}} band-aid for popup widgets in content processes
* {{bug|585799}} band-aid for popup widgets in content processes
* '''(cjones)''' retained-content-only layer transactions
* {{bug|593243}} invalidation of content outside the CSS viewport but inside the displayport is ignored
* fix seaming, at least for simple cases (v. google.com @ 2.0 or 0.5 scale-zoom)
* shadow layer perf work
* shadow layer perf work
** PROFILE MEASURE PROFILE
** PROFILE MEASURE PROFILE
** {{bug|570625}} make ThebesLayer paint directly into shareable surfaces, remove third buffer
** {{bug|570625}} make ThebesLayer paint directly into shareable surfaces, remove third buffer
** '''(dougt/stuart)''' drawing scale-zoomed layers should not be slow
** investigate using 16bpp for opaque surfaces on mobile platforms.
** {{bug|523172}} non-sucky "basic" shmem backend for android, flush existing down the toilet
** {{bug|523172}} non-sucky "basic" shmem backend for android, flush existing down the toilet
** (no bug) track updated region, only blit that from back --> front
** (no bug) track updated region, only blit that from back --> front
*** ... unless measurements says we mostly just update the entire surface, in which case swapping and always repainting would be better
*** ... unless measurements says we mostly just update the entire surface, in which case swapping and always repainting would be better
** (no bug) smarter allocation of ThebesLayer backing buffers
** (no bug) smarter allocation of ThebesLayer backing buffers
** drawing scale-zoomed layers should not be slow
** retained-content-only layer transactions
* We should be using 16bpp for all surfaces on mobile platforms.
* {{bug|593243}} invalidation of content outside the CSS viewport but inside the displayport is ignored
** 16bpp is faster and doesn't take as much memory
* fix seaming, at least for simple cases (v. google.com @ 2.0 or 0.5 scale-zoom)
* daringfireball, pmo, and twitter all have some white regions at the top of the page
* daringfireball, pmo, and twitter all have some white regions at the top of the page
* (no bug) zoom levels are not clamped correctly - some pages like http://limpet.net/ zoom out too far, others like http://xkcd.com/ will not zoom far enough.
* (no bug) zoom levels are not clamped correctly - some pages like http://limpet.net/ zoom out too far, others like http://xkcd.com/ will not zoom far enough.
Confirmed users
699

edits

Navigation menu