I’m having a hard time getting text link styles to take with Weaver’s Moodalbox. I set them as page-wide styles in the Inspector palette, but I keep getting the default blue underlined text in my Moodal popup window. Is there a trick I don’t know about? Thanks!
The only reason mac.com would make a difference is if he was trying to
run PHP or another scripting language. mac.com runs on good old
Apache, just a very restrictive version without any extras except the
DotMac stuff that Apple gives you in iWeb.
Walter
On Dec 8, 2010, at 6:45 PM, DeltaDave wrote:
I am wondering if this is because it is hosted at mac.com
Those styles come from within the browser, and apply to anything that
the page does not explicitly style. So if you create some plain text,
and don’t apply any style to it, or if you make a link, and don’t
create any styles to govern how that link should look, then the
browser has the last word about what it should look like.
Except that I have tried both page and item-level link styles, and neither has done the job. At least not in Webkit.
It’s as if the “overlay” effect were deactivating my link styles.
On 9 Dec 2010, 1:07 am, waltd wrote:
So if you create some plain text,
and don’t apply any style to it, or if you make a link, and don’t
create any styles to govern how that link should look, then the
browser has the last word about what it should look like.
Sorted. The Mootools Suite documentation refers to an issue whereby the background color of the lightbox can take on the background color of the page itself. The equivalent was happening with my link styles.
I’d forotten that I’d created some custom link styles in the Styles palette to govern the appearance of links, I’d but left the page otherwise free of link styles. The lightbox took on this lack of styles and displayed the default colored underlined text. The solution was to add some page-level link styles to the base page (not the lightbox.html page).
The clue for me was that Safari referred to these as coming from the
user-agent stylesheet. “User-agent” is browser manufacturer slang for
“the browser itself”.
Walter
On Dec 9, 2010, at 1:35 PM, DeltaDave wrote:
So as Walter said
Those styles come from within the browser, and apply to anything
that the page does not explicitly style.
Yes, that means that another rule has superseded it in the “cascade”.
Each rule is applied based on how much “mojo” it has. There’s a
complex set of rules for how powerful each type of CSS declaration is,
and thus which one will win in a conflict.
The user-agent stylesheet is very far down the list of applicable
styling rules – pretty much anything can override it! If any attempt
has been made to style the object anywhere, that will trump the
browser’s defaults .
Walter
On Dec 9, 2010, at 1:44 PM, derekzinger wrote:
btw, what does the strike-through in the Webkit inspector refer to?
An overriden style or something?