# 1.2.6
## Changed
- The Resource Manager no longer has a world-window mode: it always opens as a GUI document. The `debug.resourceManagerWorldWindow` option, its DevTools toggle and the tick that switched an open instance between modes are gone.
- `aui-viewport`: `mode` now defaults to `browser` instead of `gui`. A page that omits the meta tag lays out against the browser-style CSS viewport and follows the window; `mode=gui` (alias `mc`) opts back in. Pages that relied on the old implicit GUI viewport must now say `mode=gui`, and WorldWindow pages must declare `mode=fixed`, since the undeclared default is now the 1920-wide browser viewport.
- `<iframe>`: the WebView2 user data directory moved to `apricity/.cache/webview`, and the resource scan, static resource list and dev auto-reload now skip dot-prefixed directories. An existing `apricity/webview` is orphaned: delete it, or move it to `apricity/.cache/webview` to keep its cookies.
## Fixed
- WorldWindow frustum culling and hit testing were built without the camera view matrix, so a panel that was on screen could be culled away the moment the camera turned, and its pointer/crosshair mapping only lined up while the camera faced the world axes. The view matrix is now composed with the pose for both.
- Root `overflow` is carried by the viewport instead of the root element's own box (CSS 2.1 §11.1.1), so a page using the ordinary `html,body{overflow:hidden}` idiom paints again. With no in-flow content the root box is zero-height, which used to collapse the clip to an empty rectangle and cull every node: the whole page disappeared with no error at all.
- Fixed the `GL_INVALID_OPERATION ("Depth formats do not match")` flood when another mod blits depth out of the stencil-enabled main render target (KubeJS's `HighlightRenderer` was the reported case). The destination's depth format is now matched at the blit call site, and the copy succeeds again.
- `<iframe>`: Enter did nothing in a single-line `<input>`, so a page's own search box could never be submitted from the keyboard; it now submits the enclosing form.
Developer information
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle.
maven { name = "Modrinth"; url = "https://api.modrinth.com/maven" }