What bothers you exactly about the standards compliance? Divs aren't
required to have classes or IDs. In fact you can use CSS to define
styles for these using either a straight div {...} or something like
#content main div {...}.
And there's nothing wrong with using inline styles, either. In fact,
I would assume the author did so in order to prevent namespace clashes
with other embedding websites' CSS - that's also one of the reasons
why it's an iframe within an iframe, as well. "Never mix presentation
and content" is a rule of thumb, not a law of the land :) It's a
question of what's appropriate.
--
Tyler Style
http://malthusian-solutions.com
http://nirdvana.com
jen wrote:
> Hello, I've just implemented greybox on a site and am pulling my hair
> out because so much styling is being done within the javascript
> instead of using id or class to let the css file take care of it. Is
> there some logical reason that window sizes are set throughout the
> javascript, that there are <div> without id or class, that there is
> styling within the html output?
>
> Here's an example of the javascript output that doesn't make sense to
> my standards-concerned eyes:
>
> <div id="GB_overlay" style="opacity: 0.7; width: 100%; height:
> 324px;"> </div>
> <div id="GB_window" class="GB_Window" style="left: 402px; top: 0px;">
> <div>
> <table class="header" style="background-image: url(undefined); width:
> 506px;">
>
> I hope your answer clears this up, as I'm really frustrated!
>
> Thanks!
> jen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"GreyBox" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/greybox?hl=en
-~----------~----~----~----~------~----~------~--~---
