Seems that you are including both webix.js and webix_debug.js files at the same time. One should use webix.js for production version and webix_debug.js during development.
They feature the same functionality in terms of components, but webix_debug features a lot of hints in case of developer mistakes.
Actually nothing more is needed once you’ve included webix_debug.js. Different debug flags are optional. I tried it locally - Shift-RightClick over some Webix component - debug context menu works well.
So now the page is opening at least. But Shift-RightClick does nothing for me, opens the regular context menu. Are there some further steps that need to be taken to debug?
As you can see I just removed width and added ‘adjust: “data”’
If you try running that page, you’ll see that again, the page simply refuses to load. And the CTRL-RIGHTCLICK Debug menu of course doesnt work, and I get a single error message in the Console:
Uncaught TypeError: string is not a function AT host:port/static/codebase/webix_debug.js:15598
Now obviously this is thoroughly useless for me since I can’t understand what I did wrong in the code change. In this situation it’s easy to revert to a working config since the change was small, but you can understand why this is a problem.
Is this a limitation of Webix? Or is there a way to debug this sort of problem properly?
What’s wrong with the adjust: “data” line and why did it cause the page to blank out?
Oh, sure its Ctrl+Rightclick, I didn’t get you, sorry. I’ll update the docs with the wrong info as well.
I don’t think using webix_debug.js is useless. You can inspect the error in console and find the place in code where an error happened. In compressed code (webix.js) it would be totally impossible.
Try using different browsers as the debug info they give may vary. In Firefox, for instance, the same error looks like:
TypeError: config.template is not a function
value = config.template(item, this.type, value, config, i);
So you understand that something is wrong with item template.
Actually, in this case you’ve found a bug adjust and template properties don’t work correctly when using at the same time.
Still, if you define item template as function, everything goes well: