line-height confusion

[foosion]

It seems a primary reason for unitless is inheritance behavior, https://developer.mozilla.org/en-US/...SS/line-height

That's not really applicable to my use case here. In any event, the point was using line-height with p wasn't working with any variation of line-height ("I've tried large and small numbers with em, unitless and %, but it always looks the same.")

I continue to think different treatment of paragraph and heading tags with respect to whether CSS line height has an affect makes little sense.

[Turtle91]

Did you try !important?? Did that have any effect?

[foosion]

Originally Posted by Turtle91

Did you try !important?? Did that have any effect?

It did not have any effect.

[foosion]

Line-height also affects div.

Found in an ebook which uses <div class="ct"> for a chapter title. Why don't they just use an h?

[Turtle91]

Originally Posted by foosion

Line-height also affects div.

Found in an ebook which uses <div class="ct"> for a chapter title. Why don't they just use an h?

Some software was written before people cared about proper semantics. Back then all styling was done in-line. With the advent of css there was a major push to use semantics only in the html file and all styling to be accomplished in the css.


Unfortunately, the programmers of those early software programs weren't paid enough to change their paradigm so their software....sucks....

[JSWolf]

Originally Posted by foosion

Line-height also affects div.

Found in an ebook which uses <div class="ct"> for a chapter title. Why don't they just use an h?

I've seen some eBooks where there was no <p>. They are all <div>. Sure technically it works, but it's crappy code.

[foosion]

For today's crappy code, a book with style="whatever" littered throughout the text. If every h2 is <h2 style="text-align: center";>, which not just put that in the CSS?? Similarly for many other tags.

Probably a rhetorical question.

[Turtle91]

You are exactly right. Semantics in the html <h2/p/div/ol/ul/table> etc to define WHAT it is… the css has how it LOOKS.

I have seen some nasty code that defined <p class="paragraph"> instead of just defining the standard paragraph css and using <p>. Of course, if you have a SPECIAL paragraph that you want to give a different look, you can define it with a class <p class="special">.

[foosion]

Originally Posted by Turtle91

You are exactly right. Semantics in the html <h2/p/div/ol/ul/table> etc to define WHAT it is… the css has how it LOOKS.

I have seen some nasty code that defined <p class="paragraph"> instead of just defining the standard paragraph css and using <p>. Of course, if you have a SPECIAL paragraph that you want to give a different look, you can define it with a class <p class="special">.

One issue with <p> is distinguishing paragraphs with a text-indent and those without. Some CSS defines <p> with a text-indent and then has a class="noindent", typically for the first paragraph of a section, while others define <p> without an indent, then add a class="indent" for every paragraph other than the first.

Is one of these more canonical?

[DNSB]

Originally Posted by foosion

One issue with <p> is distinguishing paragraphs with a text-indent and those without. Some CSS defines <p> with a text-indent and then has a class="noindent", typically for the first paragraph of a section, while others define <p> without an indent, then add a class="indent" for every paragraph other than the first.

Is one of these more canonical?

There is no such thing as canon when it comes to writing CSS. There are many ways of getting the same results and all are equally valid. There is no one true way.

Generally, I try to use the naked tag for the more common case so I would use p for the indented paragraphs and p class="noindent" for the less common scenario though I've seen several uses of the :first-child pseudo-class. My general preference is for simpler CSS where possible.

The only "canonical" item when it comes to paragraph indents is that you can use indents or spacing between paragraphs. Do not use both.

[Turtle91]

I agree. I prefer the vast majority of “standard” paragraphs to be the naked <p> and the specials to have the class. Although I also use the more complex css (with appropriate fallback coding) when I know the target device can handle it.

I don’t know that it is “canonical” to not specify indents or line-height at all and leave it to the user to set in their app/device. The flip side of that argument is that some devices/apps don’t allow that setting to be adjusted, so there should be some default…

All I DO know for sure is that I’M right and everyone else is not as good!!

[foosion]

There should be one-- and preferably only one --obvious way to do it.
-- https://peps.python.org/pep-0020/

[DNSB]

Originally Posted by foosion

There should be one-- and preferably only one --obvious way to do it.
-- https://peps.python.org/pep-0020/

Sadly, there are many ways to do most programming tasks. Back when I was at university, I took a programming class. I rapidly noticed that even if one of my classmates didn't place his name on a program listing, their programming style was enough to identify them 90% of the time. Much like identifying an artist by their brushstrokes or a writer by their word choices and the structure of their writing, most programmers 'sign' their work.

I do agree with much of what those 19 aphorisms say though beauty is in the eye of the beholder. You may not think using DAA to convert binary to ASCII hex is beauty. Others would disagree.

[foosion]

Originally Posted by DNSB

I do agree with much of what those 19 aphorisms say though beauty is in the eye of the beholder. You may not think using DAA to convert binary to ASCII hex is beauty. Others would disagree.

A nice way to see the list is to execute in Python

import this

Of course, the best import to execute in Python is

import antigravity

[DNSB]

Originally Posted by foosion

Of course, the best import to execute in Python is

import antigravity

Tried that once & it took me hours to get down from the ceiling. Never again!