You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using the <GridNoRecords> component I wish it didn't have a border by default as the entire grid has a border, I also think it would be better if it used the entire width of the grid for longer messages, and didn't overflow below the grid. Here is an example using KendoReact + material-main-dark theme.
<Gridscrollable='none'data={data}total={total}><GridNoRecords>
No active offers. Keep this page open to receive notifications.
</GridNoRecords><Column{...columnProps("QuoteID")}title="Ref"filter="numeric"/><Column{...columnProps("PickupCity")}title="Pickup"/><Column{...columnProps("DeliveryCity")}title="Delivery"/><Column{...columnProps("ResponseDateTime")}title="Bid Date"filter="date"cell={DateTimeCell}/><Column{...columnProps("EMailAddress")}title="Bid By"/><Column{...columnProps("AllInRate")}title="All-In Rate"filter="numeric"cell={statusCell}/></Grid>
Describe the solution you would like to see implemented
Above.
Describe the alternatives you have considered
Manually overriding the default styling. Downgrading @progress/kendo-theme-material as older versions didn't have this styling.
Is your feature request related to a problem? Please describe.
When using the
<GridNoRecords>
component I wish it didn't have a border by default as the entire grid has a border, I also think it would be better if it used the entire width of the grid for longer messages, and didn't overflow below the grid. Here is an example using KendoReact + material-main-dark theme.Describe the solution you would like to see implemented
Above.
Describe the alternatives you have considered
Manually overriding the default styling. Downgrading
@progress/kendo-theme-material
as older versions didn't have this styling.Additional context
The text was updated successfully, but these errors were encountered: