Hi René,

There are various CSS rules in our component for integrations like this. I am attaching a screenshot that shows where that rule comes from and how it cascades through the edited row for the grid, and another one that shows the default value for a standalone textbox.

Setting the width to 100% will work in the grid too, but you need to keep in mind that the grid cells have some default padding which CSS takes into account. You could remove it for all columns in the entire grid, or you could use the CellRender event of the column to add specific classes to specific columns/cells and cascade through them (e.g., also through the edit row) to remove padding for a particular cell in particular mode.

For the dropdowns, if you want to use CSS right now, you must use the !important modifier so your rules can override the inline style.

Here's how a sample rule would look like (available in the attached sample page too):

    .k-grid-edit-cell .k-autocomplete {
        width: calc(100% + 18px) !important;
    }

If that inline width is removed, you'd likely be able to remove the !important modifier (you'd still have to ensure your own selector is heavier than a rule coming from our themes). If that default width is replaced with something like 100%, you'd still need the !important keyword.

Regards,
Marin Bratanov
Progress Telerik

Hi René,

We are aware of this and, in retrospect, it might not have been the best idea to add such a default value. We do have it in our backlog to revise that, as it applies to all dropdowns (not just the autocomplete, also the dropdownlist, combo box, multiselect).

The key issue is that this may be perceived as a breaking change so we need to tread carefully and review it when the time comes to do a 3.0.0 release.

On a side note, the other inputs usually default to 12.5em, not to 100%. Making an input be 100% is either done by setting its Width parameter to 100% (which works for the dropdowns too), or by using CSS selectors (which may get complicated if you want it to target many different components and scenarios).

Regards,
Marin Bratanov
Progress Telerik