KeyboardManager
As far as I can tell there's no particular reason for initializing `KeyboardManager`-instances eagerly, since the user may never use editing, and we can easily do this lazily instead by utilizing shadowed getters.
annotationStorage
Util.getAxialAlignedBoundingBox
unicorn/prefer-string-replace-all
createPromiseCapability
PromiseCapability
Metadata
class
PRODUCTION
OffscreenCanvas
SetOCGState
static
GlobalWorkerOptions
id