Re: [css-d] Top margin problem from accessibility link
Le 4 oct. 2013 à 12:38, Richard Grevers a écrit : > Hi, > > At http://test.permaculture.co.nz I am trying to tighten the layout a > little in order to fit more content above the fold. > reducing the top margin of #page has had no effect, so I am guessing that > the Drupal-generated p#skip-link above it is the problem. > It looks as though the "off-left" technique has been applied to the link > inside the p rather than to the block element. > > Is it safe to give p#skip-link a zero height? correct url (thanks Richard): http://test.permaculture.org.nz/ I would make the p#skip-link position: absolute with width, top and left coordinates to taste, then adjust the margin-top for #page as needed. That would also avoid having the whole page slide down when the skip-link is focussed (that could be disconcerting for some users). IIrc, some AT software treats elements with height:0 as invisible or hidden. PS - colour mismatch for background-color in the logo image with the rest of the masthead Philippe -- Philippe Wittenbergh http://l-c-n.com __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] Top margin problem from accessibility link
Hi, At http://test.permaculture.co.nz I am trying to tighten the layout a little in order to fit more content above the fold. reducing the top margin of #page has had no effect, so I am guessing that the Drupal-generated p#skip-link above it is the problem. It looks as though the "off-left" technique has been applied to the link inside the p rather than to the block element. Is it safe to give p#skip-link a zero height? -- Richard Grevers, New Plymouth, New Zealand Dramatic Design www.dramatic.co.nz __ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Two classes, two conflicting rules, which wins ?
On 1 Oct 2013, at 16:50, Robert A. Rosenberg wrote:
So you are saying that in a 'class="c2 c1"' case, it scans the CSS defs,
> sees .c1 and applies it, keeps going and sees .c2 which overrides the c1
> width?
>
> IOW: The order that you list the class in the HTML is ignored and only the
> order that the classes are defined in the CSS defs counts.
>
On Wed, Oct 2, 2013 at 9:17 AM, Eric A. Meyer wrote:
> That's correct.
(Assuming the selectors have the same origin, weight, AND specificity, that
> is; in that case, then the order the rules are listed in the CSS matters.
> If two selectors don't have the same origin, weight, OR specificity, then
> the order they're listed in the CSS is irrelevant.)
Pertaining to origin, it's worth pointing out that the cascade also applies
when attaching external assets to a document:
HTML:
CSS:
// Same with CSS imports
@import url("other.css");
@import url("one.css"); <-- winning
[!] unless the nuclear option !important is used in one but not the other
--
Jon Reece
jon.re...@gmail.com
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
