Site feedback

shapper wrote:

On Jul 21, 12:28 am, dorayme <doraymeRidT... (AT) optusnet (DOT) com.au> wrote:
http://preview.tinyurl.com/mvhb8w

I corrected the font family errors. But I am not sure how to fix the
following warnings:

1. The color warnings.
Does this mean I always need to set a background color even if
transparent?

I would suggest that you always specify color whenever you specify
background-color, and vice versa.

2. The width on floating. So how would I style the pager list items? I
am not sure what I am doing wrong.

You could specify a width measured in em units, where the width you pick
is wide enough for the largest list item.

On Jul 21, 1:53*am, C A Upsdell <cupsd... (AT) nospam (DOT) not> wrote:

shapper wrote:
I do not see how your design requires a fixed width. *The image in your
header is 880px wide, but you could always make this a background image,
and accept that it will be truncated if the browser window is narrower
than you expect.

The image is randomly generated by the server code.
I am not able to include it on the CSS.
And in the future it might be change for a Flash movie.
I had this restrictions.
I ended up with this solution.
I admit not the best approach but given the restrictions ...

Thanks,
Miguel

On Jul 21, 1:49*am, C A Upsdell <cupsd... (AT) nospam (DOT) not> wrote:

I would specify a margin of zero, except the bottom margin, which should
be specified in em or ex units, e.g. margin-bottom:0.67em;

Just did. I changed the margin-bottom: 1em;

I also made a few more changes on my typography css styles to use em
on margin and padding.
Not sure if that is correct but it makes sense.

Thanks,
Miguel

In article
<8e7b17b5-ef26-4bc9-a062-9ba93143223f (AT) k30g2000yqf (DOT) googlegroups.com>,
shapper <mdmoura (AT) gmail (DOT) com> wrote:

On Jul 21, 2:33Â*am, dorayme <doraymeRidT... (AT) optusnet (DOT) com.au> wrote:
Are you writing and formatting this CSS or grabbing it from somewhere
else?

....

While I would not say your design falls apart, as Upsdell says, when the
user have a smaller than you expect width, I think you are designing
around a too great a width.

Sorry, you mean I should reduce the width of the web site.
If I am not wrong the percentage of people with 800 px screens are
getting smaller everyday.
This was a decision I took knowing about it ...
I completely understand your point but given the kind of people that I
expect to visit the web site and looking for many other web sites I
took a change.
I will follow the stats of the web site and check if a change to 780px
is required.
What do you think?

I think you should not have a set width at all. Perhaps you might like
to set a min and max width, up to you. But it is simply not reasonable
given your material to have horiz scrollbars coming on where yours do.

You seem to think this is all about people's screen sizes. It is not. It
is about user convenience. I have large screens but I still like to
often reduce the browser to fit other stuff on and it is an irritation
to scroll where really there should be no need. A data table with many
cols would be an understandable reason to scroll, a photographic site
with big enlargements where the interest is in the details might be
another situation where I would feel it reasonable to be scrolling. But
not for the material on your site (as I remember it).

Upsdell said something about your wide image that was sensible, consider
his advice.

--
dorayme

"shapper" <mdmoura (AT) gmail (DOT) com> wrote

On Jul 21, 1:53 am, C A Upsdell <cupsd... (AT) nospam (DOT) not> wrote:

shapper wrote:
I do not see how your design requires a fixed width. The image in your
header is 880px wide, but you could always make this a background image,
and accept that it will be truncated if the browser window is narrower
than you expect.

The image is randomly generated by the server code.
I am not able to include it on the CSS.

Make a controller called, for example CssController

Then in this controller something like:

public ContentResult Main( ) {
string css = GetYourExistingCss();
string extraCss = GenerateSomeCssWithYourRandomImage();
return Content( css + extraCss, "text/css" );
}

And in your page:
<link rel="stylesheet" type="text/css" href="/Css/Main"/>

On 2009-07-21, shapper <mdmoura (AT) gmail (DOT) com> wrote:

On Jul 21, 12:28*am, dorayme <doraymeRidT... (AT) optusnet (DOT) com.au> wrote:
http://preview.tinyurl.com/mvhb8w

I corrected the font family errors. But I am not sure how to fix the
following warnings:

1. The color warnings.
Does this mean I always need to set a background color even if
transparent?

There is a small risk of a user stylesheet intervening and changing your
transparent to white. But I wouldn't really worry about that.

It would be quite strange for a user to have a stylesheet that set white
backgrounds on things and not color, unless they were trying to make
text invisible.

2. The width on floating. So how would I style the pager list items? I
am not sure what I am doing wrong.

The warning is out-of-date, just ignore it. In CSS 2 you were supposed
to set widths on floats. In CSS 2.1, which is what everyone is working
to now, defines shrink-to-fit width and people use it for floats all the
time.

On 2009-07-21, shapper <mdmoura (AT) gmail (DOT) com> wrote:

On Jul 21, 12:28*am, dorayme <doraymeRidT... (AT) optusnet (DOT) com.au> wrote:
http://preview.tinyurl.com/mvhb8w

Dorayme,

I got free of the CSS error and solved most of the warnings.

If possible just let me know how can I solve the color and width
warnings.
I am not sure how should I do that.

Don't fix them. Check the colour ones for any real mistakes and ignore
the rest. Ignore the width warnings (they only apply in CSS 2 which
no-one is using).

These are warnings, not errors. The objective is to understand them and
decide whether to do anything or not, not to just blindly make them go
away.

In article <slrnh6athf.599.spamspam (AT) bowser (DOT) marioworld>,
Ben C <spamspam (AT) spam (DOT) eggs> wrote:

2. The width on floating. So how would I style the pager list items? I
am not sure what I am doing wrong.

The warning is out-of-date, just ignore it. In CSS 2 you were supposed
to set widths on floats. In CSS 2.1, which is what everyone is working
to now, defines shrink-to-fit width and people use it for floats all the
time.

And a beaut feature of floats it is this shrink-to-fit characteristic,
be awful without it!

--
dorayme

On 2009-07-21, dorayme <doraymeRidThis (AT) optusnet (DOT) com.au> wrote:

In article <slrnh6athf.599.spamspam (AT) bowser (DOT) marioworld>,
Ben C <spamspam (AT) spam (DOT) eggs> wrote:

2. The width on floating. So how would I style the pager list items? I
am not sure what I am doing wrong.

The warning is out-of-date, just ignore it. In CSS 2 you were supposed
to set widths on floats. In CSS 2.1, which is what everyone is working
to now, defines shrink-to-fit width and people use it for floats all the
time.

And a beaut feature of floats it is this shrink-to-fit characteristic,
be awful without it!

Quite. I hate to think of all those people with a "no warnings" policy
going around setting widths on all their floats.

Ben C schrieb:

On 2009-07-21, shapper <mdmoura (AT) gmail (DOT) com> wrote:

1. The color warnings.
Does this mean I always need to set a background color even if
transparent?

There is a small risk of a user stylesheet intervening and changing your
transparent to white. But I wouldn't really worry about that.

It would be quite strange for a user to have a stylesheet that set white
backgrounds on things and not color, unless they were trying to make
text invisible.

Consider the following.

author stylesheet:

body {
color: #000;
background: #fff
}
div#content {
color: #000;
background: transparent
}


user stylesheet:

body {
color: #fff;
background: #000
}


result:

body { /* user stylesheet wins */
color: #fff;
background: #000
}
div#content { /* from author stylesheet */
color: #000;
background: transparent /* #000 (from user stylesheet) */
}

--
Johannes Koch
In te domine speravi; non confundar in aeternum.
(Te Deum, 4th cent.)