tedd wrote:
>> Pitfalls: - repositioned "bits and pieces" may not scale well when
>> subjected to font-resizing.
>
>
> Use em's.
Using 'em' for dimensioning and positioning works just fine in some
cases, but not at all in others. It all depends of what those "bits and
pieces" are and where they're going, and although I don't have any major
problems with scaling (since I always try to design and test for the
extremes), I know that many designers/sites do, so scaling /may/ cause
problems.
>>> With css you can display things one-way for the viewer and
>>> another way for SE's -- no problem.
>>
>> I see plenty of potential problems for a number of Users if this
>> isn't done right on _all_ levels.
>
>
> I said "viewer" not user. I'm/we're talking about display elements,
> not for all users (i.e., visually impaired).
I'm not visually impaired (at least not yet), but I regularly prefer to
read, look at, or listen to, pages/sites at a non-CSS level. Not all SEO
sites make all that much sense when viewed, or listent to, unstyled, and
I see that as potential problems.
> However, outside of that, I'm not sure as to what _all_ levels to
> which you're referring.
All levels that any regular User Agent (browsers - including regular
user-options and assisting technology) base their reproduction for
visitors on, should be given optimal attention during the
design-process. By "optimal" I mean "as good as possible with the tools
at hand".
That means that non-CSS-able User Agents should not be given a
source-code that obviously is put together in a way that is less than
optimal. Users of such User Agents may not get the same experience as
users of CSS-able User Agents get, but it should be optimized.
CSS is a wonderful tool, but CSS shouldn't be used to "repair" what's
been "intentionally broken" for whatever reason. The same with
javascript and other design-tools, as they all will give optimal results
when the base - source-code - is optimized.
----
As mentioned: I usually rearrange and reposition "headers", or rather
parts of "headers", but I also make sure my source-code has the
"content-worthy" part(s) of the header on top. I think it is called:
"ordered source-code" (or at least that's what I call it), and it's a
good base for CSS enhancements.
I never bother about SE-ranking (mentioning it here since that was part
of, or reason behind, the original question), but I don't think I'm
loosing any by playing fair game and optimizing my designs on all
levels. *Recommended*.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
