Dash (Graph and DataTable) and Bootstrap do not interact well
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
dash 1.10.0
dash-auth 1.3.2
dash-bootstrap-components 0.9.2
dash-core-components 1.9.0
dash-html-components 1.0.3
dash-renderer 1.3.0
dash-table 4.6.2
- OS: Ubuntu 19:10
- Browser: Firefox 75 - Chrome 81
Describe the bug
Interaction between dash Graph and DataTable with Dash Bootstrap Components is poor.
In the attached example there are 4 tabs with 2 Graphs and 2 Data Tables
- graph: ok
- graph: wrong height with dbc. graph is flat (this happens whenever the Graph is not visible initially)
- graph: in dbc there is an annoying horizontal scroll bar for a few pixels
- graph: in dcc and dbc it only uses part of the vertical screen and in dbc there are no scrollbars
I have seen more pathological behaviour (see https://github.com/plotly/dash/issues/1168) but was not able to reproduce it yet in a small app.
Expected behavior
DBC should integrate well in DCC and the other way round. Where should this bug be filed?
Screenshots
Example source code.
scratch.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached scratch.txt example and reproduce the four tab cases involving Graph, DataTable, and Dash Bootstrap Components in Firefox or Chrome. Compare the reported sizing and scrollbar behavior, then review the related behavior in plotly/dash#1168. Done means the components integrate consistently when initially hidden or displayed in tabs, without incorrect heights or unwanted scrollbars.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bootstrap, python
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100