I think one of the great things about the CSS specifications is that they
specify how to handle errors, when rules should be ignored, etc. As long as
your hacks follow these rules and a perfectly compliant browser would read
it all correctly and ignore any fixes, that's fine. Conditional comments
Of Nick Gleitzman
Sent: Wednesday, August 22, 2007 7:23 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] When is invalid CSS okay?
On 23 Aug 2007, at 3:07 AM, David Hucklesby wrote:
After all, if I write about the Sheraton Centre in
Manhattan, my U.S.
spell checker tells me I misspelled
Gunlaug Sørtun wrote:
The hiding effect gained by 'CC' is used by many to justify hacking
and to declare their solutions valid - because the validator doesn't
complain.
It is ultimately laziness, but I don't want to have to expend the mental
effort to distinguish between invalid CSS that is
Rob Crowther wrote:
Gunlaug Sørtun wrote:
The hiding effect gained by 'CC' is used by many to justify
hacking and to declare their solutions valid - because the
validator doesn't complain.
It is ultimately laziness, but I don't want to have to expend the
mental effort to distinguish between
Hey rick,
This happened to me as I mentioned in the last issue, and When I spoke to my
client and explained to him the reason he accepted it and chosen design and
cross browser compatibility to complete valid CSS and the only thing that
doesn't validate is the mozilla custom opacity:
Parse Error
Are you serving up your hacked stylesheet to everyone, or just to those
crippled by IE?
The latter is far more acceptable than the former, in my opinion.
Mike
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rick Lecoat
Sent: Wednesday, August 22, 2007
Rick Lecoat wrote:
So, is it considered 'okay', in a web standards sense, to have a non-
valid bug-fixes stylesheet working alongside your perfect,
pristine, uiber-valid main stylesheet?
It is considered bad, but necessary and therefore acceptable by most
web designers/developers.
To give
If its only to get around bugs in IE then id also have to say its ok, its
the not the developers fault bill gates still cannot get anything right
(well not bill gates but his developers, seen as he has shown alot of
interest in web standards, his browsers still suck).
Anything apart from this id
On 22/8/07 (12:12) [EMAIL PROTECTED] said:
Are you serving up your hacked stylesheet to everyone, or just to those
crippled by IE?
The latter is far more acceptable than the former, in my opinion.
Just the victims of IE.
I'm of the opinion that hacks -- ie. workarounds exploiting browser bugs
On 22/8/07 (12:12) Georg said:
It is considered bad, but necessary and therefore acceptable by most
web designers/developers.
That's what I thought, Georg, but it's good to hear it confirmed --
seeing as how we don't live in that 'ideal world' that I keep hearing so
much about.
'Conditional
Rick,
The key thing to consider is this:
• Invalid *ML will force browsers into defective behaviour. If your
markup isn't written according to the very clear spec, the browser has
to make assumptions. Different browsers make different assumptions at
different times – you are leaving yourself
On 22/8/07 (12:57) Barney said:
? Invalid *ML will force browsers into defective behaviour. If your
markup isn't written according to the very clear spec, the browser has
to make assumptions. Different browsers make different assumptions at
different times - you are leaving yourself open to
Rick Lecoat wrote:
[..] However, I'm curious about why your personal preference is for
NOT using Conditional Comments; you seem to equate them with trying
to hide embarrassing non-valid code, and I'm sure that some designers
might use them for that.
The hiding effect gained by 'CC' is used
Gunlaug Sørtun wrote:
The real reason for me to not use 'CC' for separation, is that the
versioning goes on on HTML level and adds unnecessary garbage to every
single page.
If you happen to be designing an XHTML site and decide you want to use
server-side scripting to deliver your pages as
On 22/8/07 (14:41) Georg said:
The real reason for me to not use 'CC' for separation, is that the
versioning goes on on HTML level and adds unnecessary garbage to every
single page.
That's a very good point.
And, I was about to follow it up with I wish there was a way to use
conditional
On Wed, 22 Aug 2007 11:27:11 +0100, Rick Lecoat wrote:
[...]
So, is it considered 'okay', in a web standards sense, to have a non- valid
bug-fixes
stylesheet working alongside your perfect, pristine, uiber-valid main
stylesheet?
Personally, after working with separate style sheets for IE,
On 23 Aug 2007, at 3:07 AM, David Hucklesby wrote:
After all, if I write about the Sheraton Centre in Manhattan, my
U.S. spell checker tells me I misspelled Centre. So do I change
the spelling? I think not.
Hmm. Interesting example. 'Sheraton Center' is a placename - a proper
noun.
Have
If it's name was Sheraton Center that's how it should be spelt.
--
Stuart Foulstone.
http://www.bigeasyweb.co.uk
BigEasy Web Design
69 Flockton Court
Rockingham Street
Sheffield
S1 4EB
Tel. 07751 413451
On Wed, August 22, 2007 6:07 pm, David Hucklesby wrote:
On Wed, 22 Aug 2007 11:27:11
18 matches
Mail list logo
