5.2.1

This patch fixes a critical performance issue and should result in significant performance gains in scenes with many objects. Changes include:

• The XML3D element's 'view' property now always returns the active <view> element, even if it wasn't explicitly set through the 'view' attribute
• Fixed an issue where removing the active view element could cause errors
• Fixed a critical performance issue that was resulting in many copies of the same GL shader program being created
• Added the ability to disable opaque object sorting through XML3D.options.setValue("renderer-sort-opaque-objects", true|false)

5.2.0

This minor release adds the following features:

• Support for Web Components
• CSS transforms now support CSS transitions
• Materials can now change certain WebGL states during rendering

5.1.4

This hotfix addresses the following issues:

• #172: Added missing point material description to specification
• #177: Fixed Xflow error when removing certain elements
• #193: Fixed a case where light transformations would overwrite each other
• #194: Fixed a case where removing all instances of a light type would disable updates to other lights
• Added some more error guards to Xflow cleanup when nodes are removed from the DOM
• Fixed scaleOrientation handling in the xflow.createTransform operator

5.1.3

This hotfix contains fixes for the following issues:

• #163: <light> elements can now be given transformations directly through their style and transform attributes
• #185: Fixed a race condition in external document handling
• Fixed a bug in camera.js examine function that put the camera too far away from the object being examined
• Added a warning in camera.js examine for cases where the object hasn't finished loading yet
• Added missing toDOMString function to XML3D.Box

5.1.2

This hotfix addresses the following issues:

• #171: Objects with opacity < 1 should now be pickable again
• #170: Objects should no longer be rendered opaque if given an opacity material override
• #169: Adding an XML3D element to the DOM and immediately removing it should no longer throw an exception

5.1.1

Here comes an almost-same-day-hotfix for a couple of critical issues in the 5.1 release:

• #168 - Loading models from servers that use non-standard content-type headers should be more reliable again
• Fixed a document caching performance issue in scenes where the same model is referenced hundreds of times

5.1.0

The release of v5.1 brings the following features and improvements:

• #156 - Support for the z-index property to control drawing order of objects
• #127 - An interface to allow custom HTTP headers for external resource requests
• #123 - Better performance during resource loading using the Fetch API
• #27 - Improved garbage collection of unused resources (eg. elements that were removed from the DOM)
• Improvements to the FormatHandler interface to make writing custom mesh loaders easier

5.0.4

This is a small hotfix for the following bug:

• Fix for the display: none property not being applied properly to <assetmesh> elements

5.0.3

This hotfix addresses the following issues:

• Fixed XML3D.createElement but added a deprecation warning for this function. Should use document.createElement instead
• Changing the ID of an element just before removing it from the DOM should no longer throw an error
• CSS matrices with entries in scientific notation (eg. 3e-5) should be parsed correctly now
• Added the contains(Vec3) function to Box

5.0.2

This hotfix addresses the following issues:

• #159 - camera.js was eating mouse events that it shouldn't have
• Fixed a problem with the getters for FoV elements in camera.js
• Fixed missing getLocalMatrix function on mesh, model, light and view elements
• XML3D.Quat.from* functions will always create a normalized quaternion