Canmove, confirm, emeritus
2,798
edits
Changes
no edit summary
[[Image: Mobile-typical-structure.png]]
Fennec takes a different approach. While <code><browser></code> elements are still used to render the HTML, they are hidden offscreen. The rendered HTML is drawn into a <code><canvas></code> element, which acts as the primary interaction UIdisplay surface. This is primarily done for the ease in which panning and zooming can be done at acceptable levels of performance. A tabbed browsing environment is created by using an additional strip of thumbnails representing the currently opened <code><browser></code> elements.
[[Image: Mobile-fennec-structure.png]]
The contents of the <code><browser></code> is copied to the <code><canvas></code>. The thumbnail used to represent the "tab" is updated either from the display <code><canvas></code>, for speed, or from the <code><browser></code> if the display <code><canvas></code> is stale.
Fennec uses the new [https://developer.mozilla.org/en/Gecko-Specific_DOM_Events#MozAfterPaint MozAfterPaint] event to optimize all DHTML updates to the the primary <code><canvas></code> display surface. Whenever the contents of the web page changes, for whatever reason, we only update the areas that actually changed. We don’t repaint the entire surface unless it's absolutely required.
===Panning/Zooming===
[talk about the stack and the WidgetStack]
===Chrome Elements===
