Support Article
The need to move to HTML 5 and CSS 3 and IE10 issue
SA-6278
Summary
Q: Why do we have to move to HTML5 and CSS3?
Q: What are the Issues identified while testing IE10 in Foundation server BA?
Resolution
Question : Why do we have to move to HTML5 and CSS3?
Answer : Below are the main points becasuse of which we had to move to HTML5/CSS3–
1. VML tags – removed ( We made use of SVG which is the standard way of all the browsers would support for graphical representation of flows)
2. Xpath support – removed (Introduced JQuery xpath plugin to support for xml parsing)
3. DataIslands support – removed (Introduced Script tags for holding the xml content on the web page)
4. attachEvent – Deprecated and will be removed in IE11 (Made use of standard events like addEventListener)
5. Nonstandard events like onPropertyChange events – removed – ( Need to call explicitly the function doPropChange() whenever there is a change in property)
6. The OOTB style sheets were not compatible for IE10 HTML5 browsers. So need to change the styles compatible for CSS3 and the corresponding HTML
Question : What are the Issues identified while testing IE10 in Foundation server BA?
Answer : Attached the list of observations ObservationsWithIE10.doc captured while testing IE10 in Foundation server BA.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.