Aardvark.Dom.Server 1.1.9

dotnet add package Aardvark.Dom.Server --version 1.1.9
                    
NuGet\Install-Package Aardvark.Dom.Server -Version 1.1.9
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Aardvark.Dom.Server" Version="1.1.9" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Aardvark.Dom.Server" Version="1.1.9" />
                    
Directory.Packages.props
<PackageReference Include="Aardvark.Dom.Server" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Aardvark.Dom.Server --version 1.1.9
                    
#r "nuget: Aardvark.Dom.Server, 1.1.9"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Aardvark.Dom.Server@1.1.9
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Aardvark.Dom.Server&version=1.1.9
                    
Install as a Cake Addin
#tool nuget:?package=Aardvark.Dom.Server&version=1.1.9
                    
Install as a Cake Tool

Aardvark is an open-source platform for visual computing, real-time graphics and visualization.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Aardvark.Dom.Server:

Package Downloads
Aardvark.Dom.Giraffe

Aardvark is an open-source platform for visual computing, real-time graphics and visualization.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.1.9 135 5/19/2026
1.1.8 155 4/28/2026
1.1.7 144 4/28/2026
1.1.6 123 4/27/2026
1.1.5 140 4/26/2026
1.1.4 135 4/26/2026
1.1.3 132 4/26/2026
1.1.2 138 4/26/2026
1.1.1 136 4/26/2026
1.1.0 139 4/25/2026
1.0.25 164 4/15/2026
1.0.24 194 4/13/2026
1.0.23 523 11/20/2025
1.0.22 367 11/13/2025
1.0.21 294 11/9/2025
1.0.20 263 10/28/2025
1.0.19 282 10/28/2025
1.0.18 263 10/23/2025
1.0.17 259 10/22/2025
1.0.16 261 10/22/2025
Loading failed

fix: picking was broken on HiDPI / Retina displays after the renderer started honoring `devicePixelRatio` (Aardworx.WebAssembly 1.2.7). `SceneHandler.HandlePointerEvent` / `HandleTapEvent` / `HandleWheelEvent` computed `pixel = original.ClientPosition - V2i original.ClientRect.Min` — CSS pixels from DOM events — and passed that straight to the pick-buffer read. With a 3× framebuffer (iPhone) the read happened at 1/3 the click location → wrong scope or none. `SceneEventLocation` also got the mismatched `pixel` (CSS) and `viewportSize` (fb), breaking any consumer doing `pixel / viewportSize` for NDC.
convert at the input boundary instead: a new `toFbPixel` helper in `SceneHandler` scales the event position via the per-event `ClientRect.Size` vs. `viewportSize` ratio — self-consistent under any `RenderControl.PixelRatio` override (no `window.devicePixelRatio` lookup needed). Pixel space stays sub-pixel `V2d` end-to-end; rounding to `V2i` happens only at the GL read-edge.
added `RenderControlInfo.ClientSize : aval<V2i>` (CSS pixel size of the canvas) alongside the existing `ViewportSize` (framebuffer pixels). Apps positioning HTML overlays via `Left`/`Top` should bind `let! cs = RenderControl.ClientSize` instead of `ViewportSize`. Shader / projection / NDC math keeps using `ViewportSize`. The split makes the unit explicit in the type — no DPR multiplication in app code. `ClientSize` is populated lazily from the first DOM event (`ClientRect.Size`); it's `V2i.II` before any event arrives, which is fine for the typical case where overlays are conditional on user interaction.