Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Verified Answer
+1
person also asked this
people also asked this
Replies
4 replies
Subscribers
8 subscribers
Views
4119 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Compatibility mode and Embedded interfaces
marky
over 8 years ago
Hello:
I am facing an error with embedded interfaces using IE11 and compatibility mode, using Appian 16.2.
In tempo.nocache.js:
Error: "'HTMLDivElement' is undefined"
While debugger highlights the following code:
(Line 49:) if(HTMLDivElement)
In this thread, the poster also had to turn off compatibility mode to get the embedded interface to work:
forum.appian.com/.../e-244547
Accessing the html in IE11 without compatibility mode or in Chrome works correctly.
OriginalPostID-250600
Discussion posts and replies are publicly visible
Parents
+1
chetany
A Score Level 1
over 8 years ago
This is mostly a browser quirk specific to IE version < 11.
IE has many quirks when it comes to JavaScript - and this applies specifically to IE7, IE8, IE9.
Things got better from IE10.
And IE11 confirms to the JavaScript implementation of other browsers like Chrome and Firefox.
Embedded interfaces require JavaScript and Ajax. And the behavior of JS is affected by browser quirks,
In compatibility mode, IE emulates the older versions and hence you may be getting that error.
In no compatibility mode, its purely IE11, and IE11 does not have as many quirks as the older versions - IE11 mostly confirms to the JS behavior of other browsers.
So, I don't think we can do much about it.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Reject Answer
Cancel
Reply
+1
chetany
A Score Level 1
over 8 years ago
This is mostly a browser quirk specific to IE version < 11.
IE has many quirks when it comes to JavaScript - and this applies specifically to IE7, IE8, IE9.
Things got better from IE10.
And IE11 confirms to the JavaScript implementation of other browsers like Chrome and Firefox.
Embedded interfaces require JavaScript and Ajax. And the behavior of JS is affected by browser quirks,
In compatibility mode, IE emulates the older versions and hence you may be getting that error.
In no compatibility mode, its purely IE11, and IE11 does not have as many quirks as the older versions - IE11 mostly confirms to the JS behavior of other browsers.
So, I don't think we can do much about it.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Reject Answer
Cancel
Children
No Data