Browser support
Brimp runs browser JavaScript with a DOM and network stack. It can execute scripts, update a document, submit supported requests, and return the resulting content. It does not render the page: there is no paint engine, compositor or browser user interface. Box layout and computed style are provided so script-visible geometry is measured rather than defaulted.
The core APIs below are available through Python, Node and the CLI. Browser subsystem plugins are enabled by default; extraction and host storage are selected explicitly. An explicit plugin list replaces the defaults.
Find an API family
Section titled “Find an API family”| Area | What works | Main limits |
|---|---|---|
| DOM and documents | HTML parsing, selectors, mutation, live collections, ranges, XPath, Shadow DOM, autonomous custom elements and measured element geometry | No XML parser; partial Shadow DOM and custom-element behavior |
| Forms and input | Values, checkedness, form association, validation, selection, numeric/date stepping and direct input | GET form submission; no pickers, validation UI or layout-based input |
| Events | Dispatch, propagation, cancellation, handlers, observers and event payloads | Many device/UI events can only be dispatched manually |
| Window and environment | Navigation, history state, timers, profile identity, media queries and font metadata | Profile values are configured; no browser UI, media playback or worker engine |
| CSS, SVG and geometry | Inline declarations, editable stylesheets, a cascade with specificity and @media, block/inline box layout, computed style, SVG DOM and attribute reflection |
No floats, flex/grid, SVG renderer or animation engine |
| Network, files and streams | Fetch/XHR, Blob/File/FileReader, streams, structured cloning and message channels | Partial browser policies and body formats; cloning can buffer data |
| Cryptography | Random values, UUIDs and the documented WebCrypto algorithms | No Ed25519/X25519 or CryptoKey cloning |
| Browser plugins | Configured browser services, canvas state, graphics/audio objects and RTC payloads | Subsystem-specific placeholders; no GPU rendering, audio processing or worker execution |
For JavaScript values crossing into Python or Node, see Values and handles.
That host bridge has a different contract from page-side structuredClone.
How to read support claims
Section titled “How to read support claims”- Implemented: the operation performs the behavior described on its topic page. This does not imply the entire web standard is implemented.
- Profile-based: the result comes from the configured browser profile rather than a live screen, device or operating system measurement.
- Placeholder: the member exists but returns a fixed value or performs no work.
A callable method may return
undefinedeven where a browser returns a Promise. - Unavailable: the interface or capability is absent or rejects the operation.
Check behavior as well as presence. For example, element.scrollIntoView() is a
no-op, getComputedStyle() reports cascaded values but no painted pixels, and
media play() rejects.
These methods cannot be used as evidence of rendering or playback support.
Examples and detailed contracts
Section titled “Examples and detailed contracts”Each topic starts with practical capabilities and limits. Expand Detailed behavior and edge cases when you need conversion rules, state lifetime or a specific difference from Safari. The runtime test suite and field ledger provide the corresponding evidence.
Browser-library regressions exercise real applications and packages. Detector results remain observations; they do not define new product capabilities or promise that Brimp is indistinguishable from a browser.