Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><em>I'm not sure if this post is a comment or an answer, but I completely agree that <code>max-width</code> is too often ignored or even looked down upon and would like to present my two cents on the topic.</em></p> <p>For most media queries, <code>min-width</code> is without a doubt the best approach. A common scenario is <code>float</code>, where you rarely want floated elements on a slim screen but still want them to float on larger screens, so you simply add the <code>float</code> through a <code>min-width</code> media query.</p> <h2>Generalized, the reasoning is that <em>it's better to add something once it's needed rather than removing it when it's not.</em></h2> <p>Since you almost always add more CSS to larger screens rather than vice-versa, it makes sense people limit themselves to <code>min-width</code> media queries. </p> <p>But what about the scenarios when you actually <em>do</em> add CSS that's exclusive to the smaller screen?</p> <p>Perhaps you want to replace text with an icon and have to do it through pseudo elements, perhaps you're doing layout changes with CSS for small screens. Perhaps you need to change some colors or add a <code>margin</code>/<code>padding</code> to the smaller screen. </p> <p>It doesn't really matter, the point is that sometimes you want to add something to a smaller screen that's not supposed to be there on the larger screen. So, following the previously stated reasoning, in those scenarios it makes sense to use <code>max-width</code> instead of <code>min-width</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy does mobile first responsive design tend to not use max-width queries alongside the min-width queries?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNils Kaspersson
    1. USNils Kaspersson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy does mobile first responsive design tend to not use max-width queries alongside the min-width queries?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COI think this is the best explained answer, especially the point about it being better to add something when needed rather than removing. Basically, the ideal goal when developing a site should be to never override a style. If you plan your styles in such a way that the ones that will only apply to small screens go in `min-width`, and the ones that only apply to large screens go in `max-width`, you will have some pretty clean styles. Can this be difficult to plan, and more work than it's worth? Absolutely.. but it's always a good goal to strive towards.
      singulars
      1. PO
      1. USBlake Mann
    2. CO@BlakeMann, also, you could define basic styles and then build upon them with min-width. And then any styles (like styles for small screens that do not apply to large screens) can be isolated by combining a min-width with a max-width media query (`(min-width:x) and (max-width:y)`). That's not difficult to plan, and actually simpler than only using min-width, since you don't have to override anything anymore, you can just isolate it.
      singulars
      1. PO
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload