Expand description
Type definitions for various types of callbacks, as well as focus and scroll handling
Structs§
- Stores a function pointer that is executed when the given UI element is hit
- Information about the callback that is passed to the callback whenever a callback is invoked
- Callbacks that returns a rendered OpenGL texture
- Information about the bounds of a laid-out div rectangle.
- Callback that, given a rectangle area on the screen, returns the DOM appropriate for that bounds (useful for infinite lists)
- Gives the
layout()
function access to theAppResources
and theWindow
(for querying images and fonts, as well as width / height) - Pointer to rust-allocated
Box<LayoutInfo<'a>>
struct - Iterator that, starting from a certain starting point, returns the parent node until it gets to the root node.
- The two-way binding system
- Pointer to rust-allocated
Box<RefAny>
struct - Information about a scroll frame, given to the user by the framework
- Callback that can runs on every frame on the main thread - can modify the app data model
Enums§
- Defines the focus_targeted node ID for the next frame
Constants§
- The screen does not need to redraw after the callback has been called.
- After the callback is called, the screen needs to redraw (layout() function being called again).
Functions§
- The actual function that calls the callback in their proper hierarchy and order
Type Aliases§
- Callback function pointer (has to be a function pointer in order to be compatible with C APIs later on).
- This type carries no valuable semantics for WR. However, it reflects the fact that clients (Servo) may generate pipelines by different semi-independent sources. These pipelines still belong to the same
IdNamespace
and the sameDocumentId
. Having this extra Id field enables them to generatePipelineId
without collision. - A callback function has to return if the screen should be updated after the function has run.