must be them homos
Feb 2, 2006 @ 23:05
God really does hate New Orleans. Wow.
log jam flim flam
Feb 2, 2006 @ 22:04
Ok, so you know when you create a CSS-based web layout using the float style? And you've got some container with navigation floating left, and then you content floats after that... and sometimes the content in too wide, and the content float drops down under your nav float... since floats are liquid and that's what they do? Isn't that annoying? Why is it that is seems to happen in IE6 when it doesn't happen elsewhere?
Well, we develop on Macs at work, and we don't check every single page in IE6 all the time. The non-design type people are all using PCs and IE6, so when this float problem happens they'll come to us developers and say, "the page is broken" or "the page is screwed up" or "something is wrong with the page" or some such variation of something. And we'll be like "what do you mean 'broken?'" and load it up in Firefox or Safari and it will be fine. And they'll say, "it doesn't look like that on my computer!" At which time, of course it clicks, and we check it out in IE6.
I think it needs to be named something as to avoid all the confusion and just get straight to the problem. I suggest calling it "dropping a float" since that's pretty much what is happening.
Of course, "dropping a float" certainly may invoke a few giggles when people perhaps make the association with "floaters." You know... poop.
Which brings me to the point of this whole post. Since the problem is called "dropping a float," I think if you caused the problem because you didn't check your page in IE6, then you "forgot to flush."
That's right, if your floats are falling below your navigation and you don't know it, you forgot to flush.
Kids: Remember to flush!
damnit google
Feb 2, 2006 @ 15:21
Dear Google that I used to love,
I think you know where this letter is going, but allow me to continue anyway. The only way I know whether or not it is a holiday is by the changes you make to your logo on your front page. Why didn't you change your logo for Groundhog's Day this year?
Sincerely,
me
dear web masters
Feb 2, 2006 @ 13:37
I'm not kidding... really... we need to start a movement...
The web community should start flooding the bug reporting for the IE 7 beta with reports about CSS and XHTML/HTML standards non-compliance. Anything IE 7 does that isn't in line with web standards should be reported as a bug, by as many people as possible. And we should keep reporting these, daily, until the IE team wakes up to web standards and decides to support them.
Reporting IE 7's security bugs and memory leak bugs... that's not the kind of beta testing we need to care about.
And when we've won, and IE 7 supports web standards, webmasters can make one version of their website that works in all modern browsers. Oh happy day. The IE team won't have to worry about supporting the weird IE quirks... people who haven't upgraded and are still using IE 6 will continue getting the same hacks that fix IE 6 and are ignored by Firefox et al, and IE 7 can ignore them just the same.
Seriously... it's best for everybody. Here, I'll help get you started:
IE 7 Development Blog
A call for feedback on their blog
BUT, I still think flooding the official bug reporting channels would be best. As far as I'm concerned, if they don't implement CSS in line with the stanards, that IS a bug.
What's really going to piss me off is when they "fix" the hacks but not the non-compliance... AND on top of it they support some CSS 3 stuff in a non-standard way so we can go through this all over again when IE 8 comes out.
Paul's on board... come on people! Joiiiiiiiin ussssss! [zombie voice]