Hello,
We have come across an issue in Chrome when it comes to dynamically enabling any complex style editor (basically anything other than jqxInput). When we call {disabled: true} in the API for these inputs, the element does indeed become enabled, but it is no longer visible on the screen. This has been determined NOT to be an issue in any of the other browsers we support (IE, Edge, FireFox, Opera). This behavior is not consistent across the board, below are the conditions that have finally been identified to cause it:
– Must be running fairly late version of Chrome (we are running Chrome 60.0.3112.101 (Official Build) (64-bit))
– Element must be ‘float: left’
– Another JQX input must be on the same line that is NOT ‘float: left’
We are running the June release, and this has only recently become an issue, so we are thinking Chrome is the culprit? We did play with the 5.1.0 release with same results.
In troubleshooting, we discovered another condition (only in Chrome) that produces similar results:
– If the div container holding the JQX inputs does not have a height assigned to it, when you call {disabled: true} the element will disappear.
I have put together a sample at:
You will notice ‘myNumberInput’ disappear when you click the button. If you add class ‘left’ to ‘myNumberInput2’, the issue is resolved. Also, if you remove ‘min-height’ from class ‘line’ in the css file and press the button, you will see how all of the inputs act incorrectly.
Thanks!
