-
Notifications
You must be signed in to change notification settings - Fork 899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EUWE] Fix IE11 VMRC connectivity #15220
[EUWE] Fix IE11 VMRC connectivity #15220
Conversation
@himdel can you please review. |
@@ -328,13 +322,14 @@ | |||
} | |||
console.debug("VMRC: is ready to start."); | |||
|
|||
if ($.browser.msie) { | |||
isIE = #{is_browser_ie?}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
var isIE
please
Except for the global var, LGTM 👍 Ah, and you may also want to remove the |
@himdel Fixed global var reference (had to be lack of caffeine..) and updated bower.json as well. I referenced the upstream PR in the commit message for historical context. |
Checked commits bmclaughlin/manageiq@bab293d~...82dd974 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Looks good. |
Verified VMRC connectivity in IE10, IE11, Edge, Chrome and Firefox during unit testing (Linux & Windows).
@miq-bot add_labels ui, bug, blocker
https://bugzilla.redhat.com/show_bug.cgi?id=1414869