Tina Clarke wrote:
>No that's not it .. that was me trying to see if the white would go away ...
>I'm guessing, though I've not tested it yet, that Thierry is right.
>
>That colour above is grey not white .... even i can read that right off:)
>
>[...]
>
>MMMmmmm I appreciate you took the time to look at the code ..
>
>(thinking: however you did not test it first (obviously) and gave me a
>wrong answer, which btw was so obviously wrong because otherwise the colour
>code would be saying white!... I tell you this for your own elucidation. )
>(and thinking perhaps before trying to answer cleverly you first take the
>time to test the answer)
>
>Why you feel the need to point out the obvious to me, re your 'golden tips'
>and word comments I've no idea really. You were wrong there too, however on
>one point.
>
>the idea that fp03 and international html/css standards of w3c don't have
>anything in common and further to that .....
>
>Always check your web editor (which includes np) pages in different browsers
>(and there are more than two btw) and with the validators, one checks with
>them no matter what editor one is using.
>
>Tina
>
francky says:
no doubt I've a lot to learn, but in the meantime:
1.
If it was you, "trying to see if the white would go away", you garbaged
it too fast (should have seen it is working - no question about it needed).
2.
I did not mean that it was *your* code with the grey in it (it wasn't),
but that it was *the code that had to be implemented* to get what you
wanted. Sorry if my reaction was perhaps too cryptical. ("see the happy
violin" = my kind of humor = in this way it fiddles o.k.)
3.
Before I send any comment to the list, I'm checking my suggestions (with
at least html-/css-validation, often WAI-validation or speed test, and
mostly in 6 different browsers to see the optical result). When I am not
sure, I say that or don't give a suggestion. - I don't always include
the testing files. The testing files I used for my tip to you was this
one <http://home.tiscali.nl/developerscorner/css-discuss/fp-tips.htm>,
linking to this one
<http://home.tiscali.nl/developerscorner/css-discuss/rightmenu.htm>.
Check please! ;-)
4.
If my monitor is not showing wrong colors, I thougt I would be the grey
you needed instead of the white. So: "... a wrong answer, so obviously
wrong ..."? Or perhaps I completely misunderstood your starting question
("What am I doing wrong with the ezine sign up box so that it appears in
white?").
5.
In his reaction, Thierry Koblenz said just the same "It's your TD. Try:
td {background:red} to see what I'm talking about. [...]".
- Because of time difference or a mailing retard I found his suggestion
after I send mine, otherwise I shouldn't have spend my time to
explore/react. Anyway, I came independently to exact the same
conclusion, and added which TD's it where and what to do.
6.
m/f was shorthand for masc./fem. (could also have said: f/m)
7.
Mostly Firefox is enough as checkpoint to see if a webpage of someone
else is IE-only, apart from the need to test in more then 2 browsers if
you are developing a page yourself. My recommendation for especially
good testing when a page is made with MS FrontPage was based on my
experience, which goes to FP2000 (giving proprietary IE-only code before
you know) - hope FP2003 is better - but this is off-topic.
8.
More off-topic: thanks for caring about my elucidation. As professional
in adult education (about 25 years ago I got an universital degree in
social sciences and pedagogic) I always enjoy deliberate positive feedback.
9.
End of my postings in this topic:
cheers,
francky kleyneman
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
