[jira] [Created] (CLOUDSTACK-2005) Condition mapping entries / rules are not working as expected

["Minying Bao (JIRA)" <ji...@apache.org>]

Minying Bao created CLOUDSTACK-2005:
---------------------------------------

             Summary: Condition mapping entries / rules are not working as expected
                 Key: CLOUDSTACK-2005
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2005
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VNC Proxy
    Affects Versions: 4.2.0
         Environment: Build No.#133 (CloudStack-non-OSS-MASTER-133-rhel6.3.tar.gz)
XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr Server, Win7Entx64SP1 for Client machine. 
            Reporter: Minying Bao
             Fix For: 4.2.0


Steps
Setup the CloudStack environments with build 4.2#133.
Add template and then create as an instance.
Manually modify the "condition mapping entries" in the ajaxkeys.js file, synchronize the script to v-2-VM.
Launch the VM via ConsoleProxy in client machine, to check if the "condition mapping entries" are working as expected.

Note
The requirements link have the following list of rules/conditional mapping entries: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Non-US+Keyboard+Support+for+Console+Proxy

Conditional mapping entry   { 
     type: <event type>, code: <mapped key code>, modifiers: <modifiers>,
     shift : <shift state match condition>,                -- match on shift state
     guestos : <guest os match condition>,         -- match on guestos type
     browser: <browser type match condition>,      -- match on browser
     browserVersion: <brower version match condition>      -- match on browser version
}

Expected Result
All the condition mapping entries / rules should be working as expected.

Actual Result 
Condition mapping entries / rules are not working as expected.
Please refer to attached for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira