Confirmed users
586
edits
(→Rules) |
(→Rules) |
||
Line 23: | Line 23: | ||
* Java must maintain one set of properties (offset, size, zoom, page size, and display port margins). The compositor must query this metrics object on every frame. | * Java must maintain one set of properties (offset, size, zoom, page size, and display port margins). The compositor must query this metrics object on every frame. | ||
* When the browser displayed document changes (e.g. tab switch, page load), java must be told of updated viewport properties (offset, zoom, page size) via the compositor when the first frame of the new content is composited. | * When the browser displayed document changes (e.g. tab switch, page load), java must be told of updated viewport properties (offset, zoom, page size) via the compositor when the first frame of the new content is composited. | ||
* When the composition-related properties (offset, zoom, page size) of the selected tab change without the document changing, java must be told synchronously from browser.js | * When the composition-related properties (offset, zoom, page size) of the selected tab change without the document changing (e.g. a meta viewport tag is added that changes the zoom, or javascript on the page calling ScrollTo), java must be told synchronously from browser.js. | ||
* When the user performs pan/zoom actions, Java should send updated properties (offset, zoom, display port margins) to browser.js. (These may be throttled, such as when we know the newly visible area is still inside the previously-painted region, or in the middle of a pinch zoom.) | * When the user performs pan/zoom actions, Java should send updated properties (offset, zoom, display port margins) to browser.js. (These may be throttled, such as when we know the newly visible area is still inside the previously-painted region, or in the middle of a pinch zoom.) | ||
* browser.js must ignore viewport-dependent events (including clicks, double-taps, and viewport updates) from java during the period where the browser content document is different from the browser displayed document. Java may still update its own viewport properties for the compositor's benefit. | * browser.js must ignore viewport-dependent events (including clicks, double-taps, and viewport updates) from java during the period where the browser content document is different from the browser displayed document. Java may still update its own viewport properties for the compositor's benefit. |