There is a heavy display issue introduced in version 4.2.1. I was not able to fully find the root of the problem till now, however, I would like to inform you already now about this, even I do not have a minimal example showing the problem.
I use jqx-ribbon inside a jqx-splitter and with height/width 100% (“fluid”). If I take the same jqx-ribbon out of the jqx-splitter, there is no issue.
There are also new small display issues, if I use jqx-ribbon in a jqx-window.
All my code uses jqWidgets with AngularJS [Version 1], but I do not know whether this has an impact on this or not. (And yes, I initialized jqx-ribbon in the
initContentcallback of jqx-window.) I use jQuery 2.2.4.
Demo of jqx-ribbon 4.2.1 [inside jqx-splitter]:
Demo of previous jqx-ribbon (4.1.2) [inside jqx-splitter]:
Demo of jqx-ribbon 4.2.1 [inside jqx-window]:
I hope you will be able to see, what is wrong. It always takes very much time to trace down such a problem to see what is really causing the issue since your demos all works perfectly. So if possible, I would like to avoid that, you surely understand…
- This topic was modified 3 years, 10 months ago by badera.
Thank you for your feedback. We tried to reproduce the reported issues using the following examples:
jqxRibbon works as expected in these instances, though. Please take a look at the examples and share if we should change anything in order to reproduce the issues you experience. Please also specify if there are any errors thrown in your browser’s console when running your code.
We are looking forward to your reply.
Thanks for the feedback.
No, there is no output on the console.
There is a main difference in your examples and my project: I use angularJS:
<jqx-ribbon jqx-instance="jqxRibbon" jqx-settings="jqxRibbonSettings" jqx-create="jqxRibbonSettings">...<>
Well, I will also try further; however, since I already lost hours earlier tracing down such things which often also turned out to be a bug, I like to avoid that if possible… But I know that you also do your best…
Thanks and best regards,
Here is an AngularJS version of the first of the above examples (jqxRibbon in jqxSplitter): https://www.jseditor.io/?key=fluid-size-jqxribbon-in-jqxsplitter-angularjs. As you can see, it works as expected. Please note, however, that the ribbon has to be initialized in the splitter’s initContent callback function.
Hmm, the problem is that there is nothing written in the doc of jqx-splitter that there is an initContent callback… I am sure this is the problem. I will check…
- This reply was modified 3 years, 10 months ago by badera.
OK, I can confirm. If I put the ribbon creation inside initContent of jqx-splitter, the ribbon behaves correctly then. So the problem is that it is not documented in the API doc of jqx-splitter, that there is an initContent callback, which should be used.
Well, I have a lot of jqx-grids in jqx-splitters also. Currently, they seem to work correctly. Should I initialize them also in the initContent?
As far as the issue of jqx-ribbon in jqx-window is concerned, I think I also have a trace: Even though I initialized the ribbon inside initContent of the window, I have jqx-sliders there, which I do not initialize in the initContent of the ribbon. So this may be the cause of this.
What can be the cause that in previous versions of jqWidgets it was not necessary to put all in the initContent of the parant and now it is?
Thank you for your feedback. We will document initContent. It is not necessary to initialize the grids in initContent if there are no issues with them, but doing so is recommended.
There have been some performance improvements in jqxRibbon that may have an effect on the initialization speed of the ribbon in an AngularJS environment (i.e. the ribbon may be initialized faster than the splitter, hence the need to use initContent).
Thanks for the clarification!
You must be logged in to reply to this topic.