Comments (5)
Thanks for your feedback. Your solution could work on desktop but we have the same problem on small screened devices.
We're going to consider how we can potentially relayout this content where we have a small viewport to display it in.
from developer.chrome.com.
FWIW, if the mobile devices constitute only a negligible portion of views you could go with this trivial solution of increasing the width first, then fix it properly in the future...
from developer.chrome.com.
I think there's an easy thing we can do to really improve this page. Our lists currently have left/right margins applied to them so they appear inset when they're inside body copy. But we're not removing those margins when lists are inside of tables so they're getting crushed.
Here's the above screenshot if we remove the margins.
I bet there's more we can do to improve the appearance of text inside of tables. I just did some fairly baseline styles for them but now that they have a lot of real and varied content, we can tweak things.
I don't think we should increase the overall line length of the page much (though we could bump it up a tad if folks want). But you don't want line lengths to run longer than around 60-80 chars because it becomes harder to read (the eyes struggle to read text on very long lines).
Wikipedia is a good example of a site that does this poorly. They don't constrain line lengths at all, so you end up with this:
Compared to something like Medium which constrains the line length to something like the 60-75 char range and is easier to read.
from developer.chrome.com.
Indeed, Wikipedia is unreadable without a custom userstyle, but the blog example is also not ideal as 79 characters is too little for documentation, which is not a short blog article, it's a technical reference with complex formatting.
from developer.chrome.com.
The original problematic table is readable now so I guess this issue can be closed.
from developer.chrome.com.
Related Issues (20)
- H
- Master
- ctrl+f in console will find results inside console.table() generated cells, but will not properly highligh those results HOT 1
- Forgot password | Can't log in | Facebook
- content: TODO HOT 1
- https://github.com/duncan76918/glowing-guacamole.git
- Ui
- Good
- Good
- GitHub Support
- cloudflarestatus.com/api/v2/status.json
- content: TODO
- Chrome
- Samsung
- Issue bug report HOT 2
- > Browser: Google
- URL: //
- Allow webSerial for Chrome Android HOT 1
- > Not blocking - is bumping Kotlin and the compiler require from accompanist? Just wondering if the transitive Kotlin bump here is worth it (or if that bump would be transitive anyway from base Compose)
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 developer.chrome.com.