Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should responsive design be a requirement? #10

Closed
stevefaulkner opened this issue Apr 16, 2015 · 6 comments
Closed

should responsive design be a requirement? #10

stevefaulkner opened this issue Apr 16, 2015 · 6 comments

Comments

@stevefaulkner
Copy link

No description provided.

@astorije
Copy link
Member

I vote 👍 on this!
However, keeping a stylesheet as simple as possible is the easiest way to be responsive. When you look at it, current specs are not too bad at being responsive...

@darobin
Copy link
Member

darobin commented Apr 16, 2015

But keeping things simple isn't always enough. The two primary offenders are tables and pre blocks. Those tend to perform poorly at low widths. Ideally the styles should cater to that with proper overflowing and the such.

@astorije
Copy link
Member

I completely agree @darobin, I was just making a general (useless?) comment.

@liamquin
Copy link

On Thu, 2015-04-16 at 07:43 -0700, Robin Berjon wrote:

But keeping things simple isn't always enough. The two primary
offenders are tables and pre blocks. Those tend to perform poorly at
low widths. Ideally the styles should cater to that with proper
overflowing and the such.

Responsive design is a technique. The requirement would be, should the
site cater to devices of different widths, such as 9-character-wide
uppercase-only portable telephones and 4-metre display walls. Although
responsive design may be (and usually is, today) at least part of a
solution for that, it's not the only possible one.

Making the specs mobile-friendly and epub-friendly might indeed
involve limits on the complexity and size of tables, perhaps with the
option to serve alternate content in some cases, for example
transposing wide tables to be tall narrow tables.


Reply to this email directly or view it on GitHub:
#10 (comment)

@jensimmons
Copy link

Yes.

The page should work for all sized screens. No reason not to, imo. If you are wondering who would ever read a spec on their phone — well, I did just the other week. Sat at dinner and read one spec start to finish. I thought I'd printed it out and brought it with me, but I'd printed the wrong one.

@fantasai
Copy link
Contributor

File separate issues if there's something specific that's broken. Responsive design in general is obviously a requirement: it's a fundamental principle of how the Web's layout systems are designed, and why the CSSWG spends so much of its time defining 'auto'. https://twitter.com/sgalineau/status/233244223837720576

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants