Christian Montoya wrote:
I'll probably be using conditional comments for the next five years,
and everytime I use them I think to myself, this would just be easier
if IE worked the same as FF/Opera/Safari.
It sure would, but would IE be 'MSIE' then? :-)
Besides, I think someone will have to
On 10/13/05, Peter Firminger [EMAIL PROTECTED] wrote:
If you've gone against all sane advice and used CSS hacks then you knewexactly what you were in for with future browsers and potential problems.Don't look at me.
I don't want to see an M$ bitch session develop here while Microsoft
If you don't use CSS hacks you have 2 options.
1. Avoid CSS that is buggy in a browser.
2. Use other hacks like conditional comments. (Conditional comments
*are* hacks, there just intentional ones)
Number 1 is simply not an option unless your willing to look like
useit.com or something. Number
Peter Firminger wrote:
If you've gone against all sane advice and used CSS hacks
then you knew exactly what you were in for with future
browsers and potential problems.
...
Sorry for the smug told you so, but many people including
myself have made this very clear over the whole life of
On 10/13/05, Peter Firminger [EMAIL PROTECTED] wrote:
If you've gone against all sane advice and used CSS hacks then you knew
exactly what you were in for with future browsers and potential problems.
A hack is a hack is a hack. Calling a hack a conditional comment
doesn't magically make it
That's not really true, Alan. A site without CSS hacks does not
necessarily have to be ugly. I develop table-less ASP.NET sites using
CSS and I have never used a single CSS hack or conditional comment,
yet my sites are still clean, good-looking and functional in the
leading browsers (IE, FF,
On Oct 13, 2005, at 12:55 AM, Geoff Pack wrote:
If the IE team fix the CSS hacks and also fix the bugs the hacks
are used to work around (as I think they originally mentioned they
would), then the hack users will be fine.
And if not, then it's no worse than having to update your
Ben Curtis wrote:
As a general rule, Only hack the dead. The only safe bug to exploit
is one that is fixed in ongoing generations of the product, or will
never be fixed because the product is dead. All other necessary
targeting should use features, not bugs. (Some may ask what the
difference
MS have fixed the * html hack for IE7, which isn't a bad thing provided
the rest of the engine comes up to scratch.
I think the article acutally makes a pretty good case for throwing IE into
quirksmode and developing for one (lousy, but reasonably predictable)
version of IE instead of four (5,
I personally think that this will be unrealistic for the time being. But
it's nice to hear that the IE team is starting to take a stand agains
the problems their buggy software created.
http://blogs.msdn.com/ie/archive/2005/10/12/480242.aspx
**
On 10/13/05, Alan Trick [EMAIL PROTECTED] wrote:
I personally think that this will be unrealistic for the time being. Butit's nice to hear that the IE team is starting to take a stand againsthe problems their buggy software created.It sounds more like they are taking a stand against the designers
what do you mean by conditional comments? It seems to me, that css
hacks are not really a good thing since they are called hacks. The
language should just work regardless of browser or computer. I think
thats what standards are for aren't they? So that the language is
standard for everyone??
Did you read the blog post in the link? The writer insists that developers use conditional comments, and even shows how to use them. What I am saying is that IE should be eliminating the need for both conditional comments and hacks. I'm not saying to take their functionality away... it's a nice
I read the first part and even went to the websites of the hacks it
gave references to. I thought that was the end of the post and then
only saw the conditional stuff after I had posted so I apologize for
that. Yes, exactly... IE needs to play nice like all the other browsers.
Buddy
If you've gone against all sane advice and used CSS hacks then you knew
exactly what you were in for with future browsers and potential problems.
I don't want to see an M$ bitch session develop here while Microsoft are
seemingly trying very hard do the right thing (at last). Obviously we have
to
15 matches
Mail list logo
