You code seems to work, but does not restore the dHtmlx 3.6 functionality.
Using version 3.6, the options were htmlencoded with < > etc.
You fix requires the options to be non encoded.
Also version 3.6 would recognize any htmlencoded options, like & ’ " or generic encodes like \.
Is it possible to ‘reverse’ your fix to supply options with htmlencoding?
I prefer the version 3.6 behaviour.
This was my first example:
[code]
[/code]
Options strings are htmlEncoded. The example shows them hardcoded inline, but my app actually receives them from a serverside component, hence the need for htmlEncoding.
Thanks,
Adri.
Get a guaranteed answer from DHTMLX technical support team
under the most suitable support plan