Release notes
Changelog
Version 1.26.0.1
Released 04 Apr 2022
| Feature | Added public interface for a custom virtual allocator to the library |
| Feature | Implemented default public virtual allocators for PlayStation and Switch |
| Feature | Added support for the clipPathUnits property for elements in SVGs |
| Feature | Added support for the image-rendering CSS property |
| Feature | Added support for the caret-color CSS property |
| Feature | Implemented the Inspector Search functionality in the Elements tab |
| Feature | Added support for the InspectorDOM domain protocol function `DOM.describeNode which could be used for automation |
| Feature | Added support for the InspectorDOM domain protocol functions – DOM.querySelector, DOM.querySelectorAll, and DOM.getAttributes |
| FeatureUnity | Update ICU library to ICU v69 and provide InternationalizationManager and BreakIterator support for all platforms |
| Enhancement | Implemented input caret navigation and selection for complex and RTL text |
| Enhancement | Update V8 to 9.4 with latest security fixes |
| Enhancement | Large SVGs used for mask-image use less memory and won’t create temporary textures larger than 1024×1024 |
| Enhancement | Added Player command line argument option for fullscreen borderless window |
| Enhancement | Implemented promise rejection event for V8 as some JS frameworks require it |
| Enhancement | Using text measure cache more aggressively to improve text layout performance |
| Enhancement | Update Nintendo Switch SDK to 13 |
| Enhancement | Update Microsoft GDK to October 2021 release |
| EnhancementUnity | Fixed performance regression from a Linux patch that is now behind a platform define |
| EnhancementUnreal Engine | Add backwards compatibility for Atlas metadata files created prior to 1.14.3 |
| Fix | Fixed crash when connecting the inspector to a page using lots of CSS variables |
| Fix | Fixed binding unsigned integers greater than 2^31 |
| Fix | Fixed a crash with complex text when the fonts used are missing the glyphs for it |
| Fix | Fixed constant redraw of text nodes that were selected at some point |
| Fix | Fixed firing of ViewListener::OnNodeTouched for TouchMove events |
| Fix | Fixed a memory leak caused by binder state leak |
| Fix | Fixed artefacts when scrolling right or center aligned text |
| Fix | Fixed trailing artefacts of elements with inherited filters |
| Fix | Fixed complex text letter spacing which was wrongly applied on overmarks and undermarks |
| Fix | Fixed attributeChangedCallback for custom elements to be called only for attributes listed in observedAttributes |
| Fix | Fixed a crash on UWP when utilizing a specific symbol on the JavaScript side |
| Fix | Fixed JS return value of the isolation property. Now properly returns “isolate” instead of “isolation” |
| FixUnreal Engine | Moved UObject creations from the Render thread to the Game thread |
| FixUnreal Engine | Fixed Compositor errors for missing textures |
| FixUnreal Engine | Initialize USTRUCT member variables that were not initialized at construction time |
| FixUnreal Engine | Fixed debug asserts due to improper usage of GWorld |
| FixUnreal Engine | Fixed soft locking when loading a streamable Texture |
| FixUnreal Engine | Added a mutex lock to prevent concurrent accessing of the internationalization manager’s resources |
Version 1.26.2.1
Released 07 Apr 2022
| Fix | Fixed InputManager gamepad null reference in Unity3d |
| Fix | Fixed a regression of cohtml.js that made it unusable in a browser |
| Fix | Fixed transitions not activating on elements with pseudo elements |
| Fix | Fixed transition state breaking when cloning nodes with JS |
| Fix | Fixed absolute element positioning when size is defined |
Version 1.26.4.1
Released 15 Apr 2022
| Enhancement | Improved performance of setting inline style in terms of CPU and memory usage. |
Migration guide
Deprecation of the IAsyncResourceResponse::UserImageData::TextureFilteringMode enumeration
The IAsyncResourceResponse::UserImageData::TextureFilteringMode enumeration is deprecated and its usage is discouraged, as it may soon be removed.
Creators should instead use the newly supported CSS property image-rendering, which allows for controlling the same functionality but for each image instance, not each image resource, offering greater flexibility. The image-rendering property supports 3 values: auto, crisp-edges and pixelated. The current implementation uses a linear sampler for auto and a point sampler for crisp-edges and pixelated.