Obsolete Known Issues
This section lists issues that only affect either previous versions of yFiles for HTML or outdated browser versions. These issues are listed for reference. Applications based on the latest yFiles for HTML-version will not be affected if viewed in a modern browser.
yFiles for HTML 2.3: Overriding properties of yFiles classes fails in TypeScript 4.0+
Since TypeScript 4.0, properties overriding accessors (and vice versa) is an error.
The yFiles 2.3 typings in fact define properties of yFiles interfaces and classes as TypeScript properties, thus overriding
properties in custom classes results in this error. The typings in yFiles 2.4+ avoid this problem.
With yFiles 2.3 and before, it’s safe to ignore these errors with a @ts-ignore comment. See the
related knowledge base article
for more information.
Rendering issues, Safari 11 and all WebKit-based browsers on iOS 11
A regression in WebKit results in rendering issues that causes missing or not correctly zoomed graph elements, seemingly broken user interaction, and other artifacts. This can be prevented by enabling the workaround cr320635 which was originally added for a Chrome bug. See the related knowledge base article for more information.
Undefined behavior with JS classes, Edge before Windows 10 version 1703
Due to a bug in older versions of Edge, JS classes may not be initialized properly. Therefore, code that uses JS classes like the yFiles demos shows random behavior like inexplicable undefined or null references when running in older versions of Edge.
Text rendering, Edge Legacy before Windows 10 version 1703
Transformed SVG text elements might be shown at wrong locations or not at all in older versions of Edge.