No post body was provided.
Use spacer components instead of CSS margins (2020)
31–40 of 230 posts
Re: Use spacer components instead of CSS margins (2020)
#32I think the main bugbear of margins that the article doesn't mention is margin collapse: I personally don't find the rules super intuitive and I would rather just be explicit with spacing than have the browser collapse things together!
One way around this is to only define margins at the end of the container.
Re: Use spacer components instead of CSS margins (2020)
#33No post body was provided.
Re: Use spacer components instead of CSS margins (2020)
#34What I would like is for a mobile site to both increase text size and reflow its contents as I pinch to zoom in on the site. Is it too much to ask ?
Re: Use spacer components instead of CSS margins (2020)
#35Quoted post unavailable.
they advocate not using margins in components not an outright ban
Re: Use spacer components instead of CSS margins (2020)
#36Quoted post unavailable.
The text of the article contains an argument to avoid margins when creating reusable components, instead allowing the consumer of the component define its margins. There is no argument made against using margin properties.
Re: Use spacer components instead of CSS margins (2020)
#37mmm, spacer elements. the new 1999 is looking pretty awesome.
The article is not arguing for that...
Re: Use spacer components instead of CSS margins (2020)
#38Quoted post unavailable.
The text of the article contains an argument to avoid margins when creating reusable components, instead allowing the consumer of the component define its margins. There is no argument made against using margin properties.
Then the title of the article is misleading and should be changed to avoid confusion
Re: Use spacer components instead of CSS margins (2020)
#39Re: Use spacer components instead of CSS margins (2020)
#40Earlier quoted context omitted.
The text of the article contains an argument to avoid margins when creating reusable components, instead allowing the consumer of the component define its margins. There is no argument made against using margin properties.
Then the title of the article is misleading and should be changed to avoid confusion
or you could maybe read the article before looking at its source code for a gotcha?