All, I wanted to take a moment to revisit this topic. As previously stated, the version of FireFox and Chrome that will be officially supported is 'Current' and 'Current - 1' simply based on some of the dependencies that we utilize as outlined earlier.
Due to Microsoft officially dropping technical support and security updates for older versions of IE [1] and IE's issues regarding dynamically updating SVG Path's documented in NIFI-207 [2] it makes sense to declare official support for Microsoft Edge. I have confirmed that the SVG Path issue is resolved in Edge which shipped with Windows 10. NiFi may continue to run successfully in older browser versions, however it will not be actively tested against them. I will be updating our website and user guides where appropriate. Thanks! Matt [1] https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support [2] https://issues.apache.org/jira/browse/NIFI-207 On Tue, Dec 29, 2015 at 10:56 AM, Joe Witt <[email protected]> wrote: > Matt > > Thanks for kicking this thread off. I personally am mostly focused on > us documenting our commitment and then working to that. Even if the > approach we have is strict such as 'current minus one' at least having > it clearly documented gives community members and users the chance to > choose wisely and provide feedback if they need more. > > Thanks > Joe > > On Tue, Dec 29, 2015 at 10:10 AM, Matt Gilman <[email protected]> > wrote: > > Folks, > > > > NIFI-1323 [1] will start working on some of the UI improvements that has > > been discussed on this mailing list recently. While planning out what we > > could introduce for 0.5.0 I realized that we don't have established > minimum > > browser versions listed anywheres. I plan to update our website with > these > > details. Below I am going to list the capabilities the UI employs and the > > external libraries we use along with the minimum versions supported by > > each. > > > > svg - (IE 9, FF 3, Chrome 4) > > localStorgage - (IE 8, FF 3.5, Chrome 4) > > jQuery 2 - (IE 9, FF (Current and Current - 1), Chrome (Current and > Current > > - 1)) [2] > > d3 - (IE 9, FF (modern), Chrome (modern)) > > codemirror - (IE 8, FF 3, Chrome (any)) > > > > We need to take the lowest common denominator amougst these dependencies. > > Due to our usage of jQuery our officially supported versions of FireFox > and > > Chrome are Current and Current - 1. While the application may run > > successfully in older browsers versions it will not be actively tested > > against them. > > > > Our current IE support is IE 9. However, in IE 10/11 there was a > regression > > that prevents SVG paths from being updated dynamically. So while we > > technically support these browsers, Connections do not move once they > have > > been created. This means if that you move a Component on the graph, the > > Connection does not move with it. This has been documented here [3] and > > references the Microsoft IE ticket as well. It appears that the browser > > that shipped with Windows 10 has addressed these issues. > > > > There are a few features we've discussed adding that would require > bumping > > the minimum IE version to IE 11 (specifically, flexbox CSS3 layout mode > and > > dropzone.js). Due to our stance on FireFox and Chrome versions I want to > > propose keeping our minimum IE version modern as well (specifically IE 11 > > in this case). This will allow us to continue building cutting edge user > > experiences and data visualizations. > > > > Matt > > > > [1] https://issues.apache.org/jira/browse/NIFI-1323 > > [2] https://jquery.com/browser-support/ > > [3] > > > https://issues.apache.org/jira/browse/NIFI-207?focusedCommentId=14262213&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14262213 >
