I just had a play with it and found this...
the CSS is fine. If you delete all the spaces and line brakes between the
list items like this
liitem1/liliitem2/lili
it fixes the probelm. Hope that helps,
Darian Cabot
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Software Engineer - Website Design
Brian
Trimming excess fat off of the code does add up over time - both in
storage
and in transfer/bandwidth
I totally agree with everything your saying. I too remove the comments
and redundant code before uploading a site. I save a commented
version, as a backup copy, so I or someone else
Brian
It works fine in IE5.2.2 Mac
Leo
Working on a navigation menu and it works great in everything BUT IE.
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting
Thanks to Darian, the extra spaces was the issue - doh! Been a long day,
been coding three different sites for 18 hours straight today!
Thanks for the feedback Leo, nice to know the Mac side is working right!
Brian
*
The discussion list for
Tom,
Please, as requested on several occasions, don't clog the list with admin
type requests, suggestions or comments as it adds to unnecessary traffic.
Instead, mail them directly to [EMAIL PROTECTED]
Thank you
Russ
individual message in the digest? That way one can just click on the
I haven't been following how things are going on PHP5, but do we have a
target on when this might be a full stable release (and then have to
really start dealing with it)?
v
On 25 Mar 2004, at 06:38, Justin French wrote:
PHP5 looks to have some VERY NICE features in the form of Tidy, which
"There's a big difference between expecting someone to update their
antiquated bowser, and shutting out the whole Mac computer platform.What you're telling us Mac people is that we shouldn't have bought that
Mac because a PC dominant $Microsoft company can't make a browser that
works to
Jamie
the main topic here is about - To hide OR not to hide stylesheets
I know what the topic is... While I agree with hiding stylesheet for the few older browsers still out there, because their owners refuse to use the better alternatives available, it is different for IE5 Mac users, because
David
Thank you, my thoughts exactly! That is the point of this discussion
tread. MSIE has interpreted the standards to suit their priorities and
just because they hold the larger market share (on the PC), their
getting away with it. We as developers, should not take it laying down
or avoid
Hi all
I don't know if this question gets recycled often here, I'm very new...
What I'd like to know is if there's a good resource that shows browser
restrictions as far as CSS compatability goes. When writing my CSSs I'd
like to know which attributes *won't* work in which browsers. I have the
On Friday, March 26, 2004, at 02:50 AM, David McDonald wrote:
From my perspective, the whole point of coding to standards means that
it doesn't matter what browser the user is viewing your site in - they
should be able to read your content regardless.
Whilst a little idealistic, yes that's the
Darian,
Rule of thumb: forget about the version 4 browsers, unless you want to
provide something like limited font tags. Even then there are
inheritance problems, but the use of these browsers is so limited now
(except, as noted by others, in some corporate in-house environments...
Optus, for
At 08:55 26/03/2004 +1000, you wrote:
I don't know if this question gets recycled often here, I'm very new...
What I'd like to know is if there's a good resource that shows browser
restrictions as far as CSS compatability goes.
This is an excellent collection of CSS resource links:
Jaime,
Good on you for persevering.
It sounds as thought the bug you are encountering is one for which you
provided a link... the inherited clear bug. The obvious (but not
necessarily easy) fix is to avoid using clear when creating parent
elements.
-Hugh Todd
The style is horribly broken on
I'm having a small problem on a page. I have a div that is located
inside another div which has a fixed width and margins: auto. The div
contains nothing more than a couple of links, and as far as my
understanding of this goes, the (default) setting of width:auto should
make the box only large
Hello All,
I'm currently developing a left-hand Nav for a site, and am experiencing a
strange problem in regard to link colors staying consistent, as well as
alignment gaps in IE...
Here are the pages:
FRONT PAGE
http://www.mcconnico.com/staging/index.html
SECONDARY PAGE
Hi
Remember, an inline element will collapse over linebreaks and cannot
have block level elements inside it.
Cheers
James
[EMAIL PROTECTED] wrote:
This email is to be read subject to the disclaimer below.
Hi Sam,
*
The discussion list
What I need is some guidance in the situation I am facing now. Should I hide the stylesheet until I fix the site for Mac IE or should I just let it be? Best person to answer would be a Mac user I reckon :)
Jamie
The immediate solution for making everyone happy is checking the user agent for IE5
Sam
You to do two thing first dump the xml prologue and second encase the
a elements as an inline list. Although a setting of does auto means
no width the links are be rendered as block elements due to spacing and
crs in your html.
Leo
On Thursday, March 25, 2004, at 11:56 PM, Sam Walker
19 matches
Mail list logo