dec 21 2013 03:18 John :
> am I right thinking this is an inheritance issue?
the descendent "nav li” selector will of course affect all such elements unless
you override them. The "footer li” selector at the linked page overrides the
display and font-size of ”nav li". Relative font size is bas
On Dec 20, 2013, at 6:00 PM, John wrote:
> at this page: thinkplan.org the footer li nav appears to be being
> influenced by the header nav li CSS and I can not see why…any clues?
think I solved it; put the top nav inside the header, renamed those header nav,
header li and that broke the in
at this page: thinkplan.org the footer li nav appears to be being influenced
by the header nav li CSS and I can not see why…any clues?
thank you!
John
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mai
dec 20 2013 20:15 Greg Gamble :
> Pages should have headers in order, with one H1 on top.
I disagree. In html5, it's perfectly correct to sectionalize different parts of
the content and have a new header structure within each section with a top H1
per section element and following headers. Th
I guess the upshot of all this is two fold...
1) We're off-topic for this list, so we should take this off-list or let it go
2) Order matters.
Thanks all.
On Fri, Dec 20, 2013 at 2:44 PM, Charles Miller wrote:
> Bet I can make some dearly-departed conscientious types roll over in their
> gra
Bet I can make some dearly-departed conscientious types roll over in their
graves by mentioning:
1. Begin with an H1 which states the subject matter as directly
and plainly as possible -- and which is white on white or placed off the page
with negative X margin. Whatever works, if
Thanks Greg
On Fri, Dec 20, 2013 at 2:15 PM, Greg Gamble wrote:
> Pages should have headers in order, with one H1 on top. Under the H1 you can
> have multiple H2 - H6's, but they should be nested correctly.
>
> Good:
> H1
> H2
> H2
> H3
> H4
>
> H3
> H4
>
> H2
> H3
> H4
>
> Bad:
> H2
>
> H1
> H4
Pages should have headers in order, with one H1 on top. Under the H1 you can
have multiple H2 - H6's, but they should be nested correctly.
Good:
H1
H2
H2
H3
H4
H3
H4
H2
H3
H4
Bad:
H2
H1
H4
H1
H4
H3
H2
There is an accessibility aspect to this too. If the text is visually not what
you want,
Nice ... helps to know what it's called when searching :-)
Thanks ...
Greg
-Original Message-
From: css-d-boun...@lists.css-discuss.org
[mailto:css-d-boun...@lists.css-discuss.org] On Behalf Of Micky Hulse
Sent: Thursday, December 19, 2013 4:00 PM
To: css-d@lists.css-discuss.org
S
dec 202013 01:16 Rick Gordon :
> I think a good criterion is this: If you were looking at the content, in an
> undesigned, purely logical order, what order would the code fall in?
Since this is headings these should make sense in an HTML5 outliner like this
one http://gsnedders.html5.org/outl
10 matches
Mail list logo
