Comments (14)
We haven't seen this issue in our testing. The normal behavior is to push the cells out of the way. Can you post either a screenshot or a notebook that reproduces the issue?
from dashboards.
Actually, the problem only seems to occur with cells that contain images/plots. The cell boundaries do not always "contain" the image. I didn't even realize that I did not size the cell correctly. I kinda wish it wouldn't let me do that.
from dashboards.
Maybe if we reversed the original thinking and clipped at the grid cell boundaries it would be less surprising? The problem then is that the notebook author can't always predict what the max size of a cell will be (e.g., table) and overflow is beneficial in that case.
from dashboards.
Maybe indicate where cell ends and overlap begins? Maybe revisit if clipping or scrolling within the cell is possible?
Investigation required.
from dashboards.
The main reason we don't hide overflow of cells is due to menus. With overflow:hidden
, menus are clipped at that bottom of the cell. Side effect is that some other elements also leak out, as seen above.
from dashboards.
One option: make borders of cells appear above cell contents, as seen below:
from dashboards.
Second option: use JavaScript to calculate the height of the cell content, and don't allow cell to be sized any smaller. This might be frustrating to users, though, since it removes some control -- it's possible a user would want there to be overflow.
from dashboards.
Also, it should be noted that when first going into dashboard view (no previous dashboard data) and when doing a show all, the cell is properly sized to contain the cell contents as they currently exist. So the only way to get overflow are: (1) the user resizes smaller than content, as Justin did in screenshot above; (2) there is a widget (such as a menu) which increases in height.
from dashboards.
Actually, I've found that during initial sizing of cell, to make it larger, the content can leak outside the cell boundary, even if I only ever increase the cell size. For example, when increasing in one direction, say width, an image within the cell increases in both width and height. Since the aspect ratio of the bounding box is not constrained, it's rather easy to get overlap when only making the cell bigger.
from dashboards.
I like option 1 for its simplicity in comparison to 2.
from dashboards.
when first going into dashboard view (no previous dashboard data) and when doing a show all, the cell is properly sized to contain the cell contents as they currently exist
When sizing a cell, we set a temporary width on the cell to cause text cells to automatically wrap after a certain point so not all text cells take the full width. This causes images larger than that size to be sized smaller than their true size. Resizing these images to be larger could then cause an overflow.
from dashboards.
PR #66 resolves this using option 1, showing cell borders always.
from dashboards.
@jtyberg give it a whirl and see if it's good enough or not.
from dashboards.
Closing. Can reopen if it's not good enough in practice.
from dashboards.
Related Issues (20)
- python does not have .order! HOT 2
- Getting error while installing Jupyter Dashboard HOT 4
- install dashboard as local user HOT 3
- Jupyter Dashboard - Plotly Charts overlapping issue HOT 5
- Clarification of "Developer tasks" HOT 3
- Demo Notebook "Scotch Dashboard" runtime error HOT 2
- Found an error in taxi_dashboard HOT 4
- How can Python code detect whether it's running in a dashboards or notebook environment?
- Is this project maintained? HOT 1
- ImportError: No module named jupyter_dashboards during installation HOT 5
- Dashboard view not showing up HOT 8
- Temporary notebook server for demos linked from wiki page is no longer active and now redirects to a site serving {ad,scam,mal}ware HOT 1
- Issue when running npm install -g jupyter-dashboards-server HOT 1
- Why move to attic?
- Dashboard view is not displayed in jupyter notebook HOT 1
- Resizing markdown cell in dashboard
- Broken in notebook>=5.6 HOT 3
- Scroll down in the dashboard mode
- Jupyter Dashboard Grid exception HOT 1
- Can't move cells in GridMode HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dashboards.