Our blazing fast Grid component built with pure JavaScript


Post by gregc »

While its a user created bug, its pretty ouchy. If you define a column with a combo and have a value in your json that is not in the list of values defined for the column, it displays something random from the list.

e.g. your row looks like this
Image
but when you click into it you can see the value that is not found
Image

it was caused because my json had "0" as the value but "0" was not in the combo values. obviously I just fix my bug to resolve it.

Last edited by gregc on Wed Feb 24, 2021 4:21 pm, edited 1 time in total.

Post by Animal »

I just checked and it does set the underlying value to the value you ask for even if there is no record in the store who's valueField matches that. So when interrogating the field in order to update some backend data, you get back what you asked for.

It just does not set the <input> value to match that, so visually it looks unusual.

Here's the ticket: https://github.com/bryntum/support/issues/2432

This is not a valid state for a combobox though. There is no selected record from its store. So if you expect some id value as the value of the combo which matches some database row, things are not going to fly. It just kind of throw up its hands and says "OK, you asked for this value, that's what I'll give you"


Post Reply