COLLECTION
I added Pointer Lock and ElementInternals to my custom browser, Omoikane. This summarizes fixes for X11 input duplication, iframe realms, form state restoration, performance degradation caused by unnecessary DOM traversal, and a garbage‑collection reference leak in Boa’s Array.from in the Rust‑based JavaScript engine, along with the necessary corrections.
I have added the Fullscreen API and TextEncoderStream/TextDecoderStream to my custom browser, Omoikane. I will address synchronization between the top layer and the native window, chunk boundaries, backpressure, decoder state that spans garbage collection, and the remaining issues identified in Web Platform Tests.
Added the HTML Popover API to the custom browser Omoikane, integrating it with DOM state, the top layer, backdrop, focus, light dismiss, as well as input and rendering.
In the Rust‑based JavaScript engine Boa used by my custom browser Omoikane, Acid3 was causing different memory errors depending on the environment, so I examined the core and fixed the weak‑reference cache for shared shapes.
When investigating a crash that occurred during Test262 execution of the Rust‑based JavaScript engine Boa due to an allocator error, I discovered that the cause was insufficient retention of the Promise during its resolution.
The stack protection we added to the Rust‑based JavaScript engine Boa was rejecting even shallow inputs because of ASAN's fake stack, so we switched to a method that reads the stack pointer directly from the address of a local variable.
In the Rust‑based JavaScript engine Boa, the unoptimized parser ran out of 2 MiB of stack while parsing valid JavaScript and aborted, so we reduced the stack usage and turned overly deep inputs into syntax errors.
When running the Boa Rust-based JavaScript engine’s Test262 on x86_64 and ARM64, only ten cases involving Float16 conversion produced different results, so I investigated the cause.