Note: I removed { from the secondaryTriggerKeys.
This has 2 motivations:
1. On different keyboard-layouts { are produced differently. E.g. on german layout "Alt + 8" is used to produce {, while most of you may use "Shift + [" to produce it. So what you may ask ?
Using german keyboard layout entering { would previously trigger the hintlist and immediately close it, due to current CHM.handleKeyEvent mechanic to work with *keyup* events.
To ensure same behaviour on every system I've removed { from the list of triggerKeys, until this issue is adressed properly.

2. Due to the small change in CHM.handleKeyEvent proposed by @redmunds the hints can now be triggered using 'Enter'.
In other words for the following fragment
```css
body {


``` 
CSS property-name hints would not pop up after you enter the { , but after you hit Enter to move the cursor into the next line.