[PfhoenixParticipant]

Thanks, that does seem to work. Any idea why the larger zIndex separation is necessary?

[PfhoenixParticipant]

It occurred to me just now why you are unable to “reproduce the issue”. There are two issues, actually :

1. 4.3.0’s source code was inconsistent with the release, minified code, where the source code had the following bug :
2. jqxTab is renaming LI IDs without checking if they have an ID or not

You guys fixed #1 by taking the bugged source code and minifying it to be the release code. You propagated the bug instead of fixing it. Can you please address this properly by fixing the bug in both source and release code?

[PfhoenixParticipant]

My bad. The following jsfiddle demonstrates what I was talking about :

http://jsfiddle.net/x7p4dfy5/10/

I’ve also been noticing the horizontal scrollbar show in these cases, and in my mind it shouldn’t. Currently, the column widths are either their widths in pixels or the grid width * column width percentage. My expectation would be the column width would either be the set width (minwidth if the column width percentage * gridwidth is < minwidth) or the column width percentage * (gridwidth – all set column widths). This would make all columns with set widths stay their expected size and would resize the percentage-based columns in order to remove the need for horizontal scrolling.

As it is right now, I don’t think minwidth actually does anything.

[PfhoenixParticipant]

I created a new to show the different ways to set the value that don’t work. I did find that calling jqxMaskedInput({ value: whatever }) works, which surprised me, since using the settings object for creation didn’t.

http://jsfiddle.net/sNbe7/161/

[PfhoenixParticipant]

When you test, please pay attention to the fact that I said the problem was with the source code you released, not the minified code. My project uses your source code when doing debugging/testing, which is how I found the problem.

[PfhoenixParticipant]

As I wrote to your support e-mail address, version 4.4.0 suffers the same exact problem as what I described with 4.3.0.

[PfhoenixParticipant]

Upon further research, I’ve discovered a difference between the minified code and source code. The difference is a check to see if the ‘id’ attribute exists or not.

[PfhoenixParticipant]

I updated from 4.1.1 to 4.3.0 today and this exact behavior popped up immediately. Prior updating, I could reference tabs by the ID I gave them. After updating, attempting to reference tabs by the ID I gave them caused an exception in jqxcore at line 4218, column 25, with an invalid selector.

[PfhoenixParticipant]

Unfortunately, upgrading to 4.3.0 just to test a bug in your library isn’t an easy option. I’m guessing also that your jsEditor and/or jsFiddle setups are using your latest version, which makes using them to test something pointless. I’d gladly setup a test page to test things locally here according to your advice, if possible.

Like I said in my original post, I my grid within the expander works properly until I try to call autoresizecolumns. Surely you have a way of testing the 4.1.1 version with the setup I’ve described.

[PfhoenixParticipant]

A listbox that doesn’t move itself within a splitter panel? Your response confuses me, due to the clarity in which I presented the issue and a reproduction case/link.

Here’s another test case, with the jumping removed : http://jsfiddle.net/Pfhoenix/az4y0ekb/3/

What’s interesting is that even setting the height for the listbox doesn’t stop it from moving up by the total height of its border. With its border hidden and a set height, the listbox no longer moves itself. This indicates to me that the bug is clearly within listbox and not splitter.

[PfhoenixParticipant]

The link didn’t make it into the post for some reason.

jsfiddle reproduction case

[PfhoenixParticipant]

Is this being addressed? There’s a forum post asking about this very problem back in January, to which the reply was “we already know about this”. Can we expect a fix for this in the next release at least?

[PfhoenixParticipant]

I think you misunderstood what I was asking. I was hoping that parentItem would allow me to avoid calling getItem for every parentElement. Is parentItem ever populated?

[PfhoenixParticipant]

Since you guys seem unwilling to do any further troubleshooting, I dug more into your theme css. Turns out, the dropdown button was being hidden because there was padding on the text input to its left. Why? Because your jqx.base.css sets padding-left and padding-right to 3px. The two themes I was testing with were ui-smoothness and arctic. UI-smoothness doesn’t modify the values set by base, but arctic overrides it with padding-left: 0px !important. After noticing this, I set both padding-left and padding-right to 0 and voila, dropdown button reappeared.

I don’t know if this is still an issue in 4.1.2, but it is definitely an issue with your css and how it renders in IE11 in 4.1.1. Not only that, I’m fairly disappointed with your level of support, not just with the general lack of troubleshooting assistance but also that you guys seem to check your forums once a day. For something my organization paid for an enterprise license for, I would expect more professionalism.

[PfhoenixParticipant]

After more digging around, I’ve discovered that the filter dropdown button is only rendering when the filter textbox is at max-width. If I remove max-width, the filter dropdown button doesn’t render at all. Is this default behavior or something I’ve done?

[Author]

Posts