This is probably question number one zillion about this subject. Even after reading Heathers Tutorial, numerous other explanations, reading and reading the stuff in CSS tutorials, I do not get it working in my site.
The LinkStylesAction does not work like in MarkUp elements or HTML elements with certain tags that get content from the database.
I have a good working p body style which shows in the stylesheet like this:
All these setting have been made in the Stylesmenu.
I tried the extended button and fill in link values there. No good result. Also validation became a huge mess after that.
What must I do there to get for just this pbody style:
linkcolour CCCCCC no textdecoration
hover colour EEEEEE no textdecoration
You need to add a style rule for the inks that are children of this
particular p style, so the declarations would look like this:
p.body a { … }
p.body a:hover { … }
Once you get the basics of the first C in CSS (cascading), the rest
will open like the heavens after a storm and pour sweet light onto
your head.
Walter
On Mar 19, 2008, at 1:09 PM, atelier wrote:
This is probably question number one zillion about this subject.
Even after reading Heathers Tutorial, numerous other explanations,
reading and reading the stuff in CSS tutorials, I do not get it
working in my site.
The LinkStylesAction does not work like in MarkUp elements or HTML
elements with certain tags that get content from the database.
I have a good working p body style which shows in the stylesheet
like this:
All these setting have been made in the Stylesmenu.
I tried the extended button and fill in link values there. No good
result. Also validation became a huge mess after that.
What must I do there to get for just this pbody style:
linkcolour CCCCCC no textdecoration
hover colour EEEEEE no textdecoration
Something did indeed change, got rid of the blue color, no line under text.
But no hovering effect, and textcolor does not match my settings.
I found this at http://www.w3schools.com/css/css_pseudo_classes.asp:
Note: a:hover MUST come after a:link and a:visited in the CSS definition in order to be effective!!
Note: a:active MUST come after a:hover in the CSS definition in order to be effective!!
How do I change the order of my settings? I cannot move them in the list, and now my a:active does not come after a:hover as they say so it does not work?
thanks
(where in the manual can I read about the background of these things? I want to know what I am doing, now it’s like moving around in the dark which I do not like at all)
Note: a:hover MUST come after a:link and a:visited in the CSS definition in order to be effective!!
Note: a:active MUST come after a:hover in the CSS definition in order to be effective!!
How do I change the order of my settings? I cannot move them in the list, and now my a:active does not come after a:hover as they say so it does not work?
Put the entire tag p.body a into the Tag field of the Style editor.
Leave the Name (class) field empty. You will have to delete what’s
there in the field and then tab out of the field in order to
completely exorcise it.
This has the added benefit that you don’t need to add the style to
any element on your page to force it to be published, any Tag-only
style is magically pushed to the page or external stylesheet. You
will need to apply your regular .body style to the relevant
paragraphs, though.
Walter
On Mar 19, 2008, at 3:32 PM, atelier wrote:
Tried that before. FW changes p.body a into p.bodya
Must I use that?
OK, finally I am starting to get control over things.
I wanted to get a hover effect by underlining the text, but that was not easy in the styles menu.
Clicking: ‘style underline’ in the text properties does not work.
Trick is to really add ‘textdecoration underline’ in the extended option.
And the tip with ‘p.body a’ works, thanks a lot for the advise.
I really do hope that FW comes with a version of the manual where one not only can read about this, but also learn about the WHY of the matter. That shall be a real timesaver for the masses that search for solutions, and for the ones (like you good folks) that want to help these poor bastards out…;~)
Glad you got it sorted out. If FW either detected link styles and ordered them correctly or gave the user the ability to drag them into their proper place it might make things a bit easier. Considering that this is a hard and fast rule it would seem a reasonable request.
Todd
On Mar 19, 2008, at 3:11 PM, atelier wrote:
I really do hope that FW comes with a version of the manual where one not only can read about this, but also learn about the WHY of the matter. That shall be a real timesaver for the masses that search for solutions, and for the ones (like you good folks) that want to help these poor bastards out…;~)
