Thierry Koblentz wrote:
height:1% or height:0 or whatever height you set gives layout to an
element, which is not the case with display:inline.
Making sure an element hasLayout is a big tool in the box when it comes to
fix IE bugs.
Just FYI, over on CSS-D there was a thread today about a web
Ian Anderson wrote:
IE7 will respect height: 1%, which if not filtered away from it could
break many layouts. They are retaining hasLayout as an internal property
and recommend using zoom: 100% for inducing hasLayout as a replacement
technique for height: 1%.
Which W3C
Bert Doorn wrote:
Which W3C standard/recommendation for CSS defines the zoom property?
I don't see it in the CSS 2.1 spec.
http://www.w3.org/TR/CSS21/propidx.html
Look in MS special non-standard instead.
If indeed it's not defined in any CSS standard/recommendation, are MS
effectively
From: Bert Doorn [EMAIL PROTECTED]
Which W3C standard/recommendation for CSS defines the zoom property?
I don't see it in the CSS 2.1 spec.
http://www.w3.org/TR/CSS21/propidx.html
If indeed it's not defined in any CSS standard/recommendation, are
MS effectively saying: We recommend you
Does this mean we're supposed to make all the sites we've ever made useless in IE5 and IE6?Maybe it's time we just give up on Internet Explorer and design for standards compliant browsers instead?The sad thing is that of course everyone who's using Explorer will blame the designer of the site and
Vincent Hasselgård wrote:
Does this mean we're supposed to make all the sites we've ever made
useless in IE5 and IE6?
No need to dump earlier versions. IE7 has some bug-fixes and somewhat
better selector-support. Apart from that it's just an IE6 which is
slightly harder to make behave like a
On 2/10/06, Gunlaug Sørtun [EMAIL PROTECTED] wrote:
Vincent Hasselgård wrote:
The sad thing is that of course everyone who's using Explorer will
blame the designer of the site and our clients will rip the hair out
of their heads because most people use IE anyway.
Don't panic...
Sit down
Wow. Microsoft are taking very pro-active measures to assist the
developer community in fixing sites for IE7.
I received an email from someone on the 'IE7 compatibility team' with a
screenshot of our site in IE7 and a list of all our stylesheets with all
the filters and hacks identified that we
Have other site owners received any similar contact from
the IE7CPTTM yet?
no can you share yours?
best
kvnmcwebn
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints
On 10 Feb 2006, at 10:49 AM, Cade Whitbourn wrote:
Wow. Microsoft are taking very pro-active measures to assist the
developer community in fixing sites for IE7.
I received an email from someone on the 'IE7 compatibility team' with a
screenshot of our site in IE7 and a list of all our
Cade Whitbourn wrote:
Wow. Microsoft are taking very pro-active measures to assist the
developer community in fixing sites for IE7.
I received an email from someone on the 'IE7 compatibility
team' with a
screenshot of our site in IE7 and a list of all our
stylesheets with all
the
Why would you hack standards compliant code for Microsoft.
Ask if they would like to foot the bill or if they had considered
writing an application that was standards compliant.
Forget that as it may not have all the bugs and vulnerabilities that
we have come to know and love.
Yours
no confidential information in the email that I can see).
Cade.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alastair Steel
Sent: Friday, 10 February 2006 11:53 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] IE7 Compatibility Team
Why
Cade Whitbourn wrote:
The compatibility issue is caused by our use of CSS filters. They
specificially highlight our use of Star HTML Hack, Selector HTML Hack
and the Holly Hack.
I'm not sure what you mean by the Selector HTML Hack.
The problem with the * html filter is that they removed it
Greetings,
From my experience when I run into an IE bug (double-margin / 3 pixel
jog) that could use height: 1% to fix it, I use display: inline as an
alternative and it saves a hack in your code or one less reason to use a
conditional comment. I haven't noticed any problems with other
Kenneth Fraser wrote:
Greetings,
From my experience when I run into an IE bug (double-margin / 3 pixel
jog) that could use height: 1% to fix it, I use display: inline as an
alternative and it saves a hack in your code or one less reason to
use a conditional comment. I haven't noticed any
16 matches
Mail list logo
