yFiles for HTML

Browser List

The following table gives an overview of the HTML5-capable browsers that yFiles for HTML has been tested with.

Legend:

The accompanying demo applications start and run.
The previous version of yFiles for HTML has been tested; the accompanying demo applications should start and run, too.
No recommendation possible.


PlatformBrowser1.01.11.21.32.02.1Notes
WindowsChrome70 -
64
63 -
56
55 -
44
43 -
42
41 -
34
33 -
29
28 -
26
25 -
21
Internet
Explorer
11
10
9
Edge
(EdgeHTML)
41.16299
(16.16299)
Under certain conditions Edge may not render text at all.
Parsing XML templates can behave abnormally for some special cases.
All of these issues can be worked around in custom code.
40.15063
(15.15063)
38.14393
(14.14393)
Under certain conditions Edge renders text incorrectly and may show repaint artifacts. Sometimes Edge may not render text at all.
Parsing XML templates can behave abnormally for some special cases.
All of these issues can be worked around in custom code.

The ECMAScript 6 demos can break randomly, see the 'Known Issues' document.

25.10586
(13.10586)
20.10240
(12.10240)
Under certain conditions transformed SVG text elements are shown at wrong locations or not at all.

Foreign object support in SVG does not work correctly with dynamic SVG. (This feature is only used in demo code.)

Firefox63 -
58
57 -
52
51 -
40
Support for touch events is disabled on desktop Firefox (bug 888304, bug 888305).
39 -
38
37 -
32
31 -
29
Incorrect JavaScript JIT optimization can cause application crashes (bug 1028990).
Support for touch events is disabled on desktop Firefox (bug 888304, bug 888305).
27
26 -
24
Support for touch events is disabled on desktop Firefox (bug 888304, bug 888305).
23Rendering issues with SVGs that are referenced from a SVG document (bug 915680).
22 -
20
19 -
15
Opera51
41
31
21
12.15 -
12.12
macOSSafari12
11A regression in Safari leads to rendering issues like missing or incorrectly zoomed graph elements, seemingly broken user interaction, and other artifacts (WebKit bug 175023). See also this Knowledge Base article.
10
9
8
7
6
5.1.7A bug in the JavaScript engine results in browser crashes with some of the demos.
Chrome70 -
64
63 -
56
55 -
44
43 -
42
41 -
34
33 -
29
28 -
26
25 -
21
Firefox63 -
58
57 -
51
50 -
40
39 -
37
36 -
29
27 -
24
23Rendering issues with SVGs that are referenced from a SVG document (bug 915680).
22 -
20
19 -
15
Opera51
41
31
21
12.15 -
12.12
LinuxFirefox63 -
58
57 -
51
50 -
40
39 -
37
36 -
29
27 -
24
23Rendering issues with SVGs that are referenced from a SVG document (bug 915680).
22 -
20
19 -
15
Chrome70 -
64
63 -
56
55 -
44
43 -
42
41 -
34
33 -
29
28 -
26
25 -
21
macOSSafari12
11A regression in Safari leads to rendering issues like missing or incorrectly zoomed graph elements, seemingly broken user interaction, and other artifacts (WebKit bug 175023). See also this Knowledge Base article.
10
9
8
7
6
5
Chrome70 -
64
A regression in Safari and all WebKit browsers on iOS 11 leads to rendering issues like missing or incorrectly zoomed graph elements, seemingly broken user interaction, and other artifacts (WebKit bug 175023). See also this Knowledge Base article.
63 -
56
55 -
52
51 -
44
23 -
21
Android
7 - 8
Chrome70 -
64
63 -
55
Firefox63 -
58
57 -
52
Opera45
Android
4.3 - 5.0
Chrome63 -
56
55 -
44
43 -
39
41 -
38
Firefox50 -
48
47 -
37
36 -
33
Opera31
25
Android
4.3
Chrome18
Android
4.2.1
native
Android
4.0.3
native
Firefox15
Windows
Phone 10
Edge
(EdgeHTML)
38.14393
(14.14393)
Same text rendering issues as with Edge on desktop PCs.
Windows
Phone 8
Internet
Explorer
10sporadic browser crashes with yFiles for HTML 1.1
Windows
Phone 7.5
Internet
Explorer
only limited interaction possible due to incomplete touch support (browser delivers no drag events)
Windows RTInternet
Explorer
11

Unsupported browsers:
Internet Explorer versions before 9 and native browsers on Android before version 4.0 are not supported due to insufficent/missing HTML5 capabilities.

Note:
Due to the dynamic nature of JavaScript implementations it is possible for an HTML5/JavaScript-based application to show different behavior depending on browser and browser version.
It is thus highly recommended that you check your HTML5-based application against your specific targeted browser versions.