The Anti-hero of CSS Layout – “display:table”

Re:The Anti-hero of CSS Layout – “display:table” by bgarbiak on Tuesday October 28, 2014 @05:56AM (#8520158)

I can't imagine a situation when using external CSS could make something to be much more difficult to understand and maintain. And no, I am not trapped by any religion, I do use inline CSS and <table> from time to time (only way to handle styling for e-mails) - and it is always a very, very painful experience.

It's simple as that: if you don't have to (e-mails) do not use inline CSS. Never, ever. And the same goes for <table>. It will actually save you a lot of work.

[ Parent | on HN ]

Re:The Anti-hero of CSS Layout – “display:table” by cpncrunch on Tuesday October 28, 2014 @01:24PM (#8522133)

It's not that external CSS will make it much more difficult to understand and maintain, just a little bit.

For example, I have a page that uses html5 to draw a playback progress bar. The canvas tag has an inline style giving the width and height. If I put this in an external css it would mean I would have to either create a new css page, or put it into an existing page (and then put a comment in the css saying which file it was for). Thus the html is larger in total, possibly more files to download, more files to maintain, and if you want to tweak the layout you have to hunt in the css for it (rather than it being right there).

In cases like this where it is a single tag, using inline styles just simplifies development and maintenance with no downside.

[ Parent | on HN ]

Re:The Anti-hero of CSS Layout – “display:table” by welly on Tuesday October 28, 2014 @11:20PM (#8525347)

Not sure that's a very good example to be honest. Why would you need to create an entirely new CSS file for this?

And adding a single comment line in addition to your style sheet isn't exactly going to break the bank.

What if your client comes back to you in a few weeks/months and says "I want another playback progress bar on another page"?

[ Parent | on HN ]