Dashboard time range filter rendering bug

[ktmud]

The time range filter in dashboard is too small, squeezing relative date range inputs.

Screenshots

How to reproduce the bug

1. Create a filterbox with time range filter
2. Add it to a dashboard

Environment

(please complete the following information):

• superset version: superset version
• python version: python --version
• node.js version: node -v
• npm version: npm -v

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven't found one similar.

[issue-label-bot]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.98. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[ktmud]

Similar issue in SQL Lab

[mistercrunch]

Related to #10302 ? @rusackas @nruhe

[rusackas]

Potentially related to that... or something else from the recent bash, perhaps. I'm not available until Monday, but have self assigned this issue to fix when I return, unless anyone else tackles it first :)

[avicenteg]

Hi,
Do you have any news related with this issue? @rusackas @mistercrunch
I think it's related with the "withTheme" function used for export the DateFilter component.

[kkucharc]

Hi @ktmud @avicenteg, do you know if this issue is still happening? I'm checking it on chrome and it looks like it was solved in meantime:

[junlincc]

@kkucharc This is happening on Dashboard time range filter, not in Explore, I can confirm that this is still an issue. reach out to me directly if it's unclear. thanks!

[avicenteg]

@kkucharc This is happening on Dashboard time range filter, not in Explore, I can confirm that this is still an issue. reach out to me directly if it's unclear. thanks!

There is any intention of fixing this? I see that you're working in preset, so maybe you know something...