I was using Very True Things as an example of something the other day and noticed something was off in the sidebar when viewed in Internet Explorer. No surprise there, but when I dug a little deeper I discovered that it was only broken in IE7 - both IE6 and IE8 were okay.
curiousPicking up from my first attempt here's a more methodical approach. With somewhat more success this time.
geeky
rushed
morosetable, tr, td and th elements) used for simple data tables and *gasp* layout tables and how their default behaviour compares with the standard CSS box model; whilst the second half would look at the "advanced" table model (caption, col/colgroup and thead/tbody/tfoot plus the accessibility enhancing attributes) and how to build complex data tables.
contemplative
relaxedI promised a test case for my latest problem and here it is: Gecko's stubborn legend.
A few things worth noting:
In reality the yellow background will be a gradiant background image within each box, so I can't just apply the background to the form.
Opera starts out displaying the upper form as FireFox does. The addition of position: relative (with no top, left, etc.) to the styles for legend magically changes that.
IE7 breaks the * html hack so some further work will be needed to align the legend horizontally without breaking things in any other browser.
Gecko doesn't seem to apply float or display (except display: none;) to legend elements at all.
busy
pissed offtop: 2px;
top: expression(26 + "px");/* suspect CSS: potential scripting: expression */
div.title { top: 26px; }
head:first-child+body div.title {top: 2px;}This morning I got on the wrong train. I have never done that on the way to work before, and I've only done it twice on the way home (and drink was definitely involved in one of those cases). So I was heading towards Victoria rather than London Bridge, and having a plain return season ticket rather than a travelcard I couldn't jump off at Balham and hop on the Northern Line. So I jumped off at Balham and waited for the next train to London Bridge, which was late and even if it hadn't been late would have gone back through West Norwood half an hour after I left.
My web server has been up and down, but mostly down, all day. I think that one of this weekend's jobs will include taking a complete backup of everything.
For some reason I bought another issue of .net magazine. This one comes with a free CSS reference poster. The credits for which read:
Reprinted courtesy of the W3C
www.w3schools.com
The poster is indeed a version of the w3schools CSS chart which explains why it's not very good, 'cos w3schools aren't very good. w3schools are also nothing whatsoever to do with the W3C. Whoops.
grumpy grumpy geekyVia a newsgroup post:
A stylesheet used on a MicroSoft web site: http://connect.microsoft.com/Styles/Gene
/* fix for the IE 1px-off margin error */ * html .StupidIEMarginHack { margin-right: 1px; } * html .StupidIEWidthHack { width: 100%; }
Even MicroSoft's own web developers are fed up with IE's CSS shortcomings.
cheerfuldisplay:block in some case only respond to mouse hovers and clicks on the text and in other cases respond to hovers and clicks anywhere in the block. I think the deciding factor is float related but I need to create some test cases to check. Unless anyone can point me towards someone who's already done the work? optimistic
indescribableSeveral changes to the default margin and padding of legends and fieldsets.This ties in directly to my suggestions on how to create Cross-browser unobtrusive fieldsets and legends and seems to screw Opera by making it apply both the Gecko and the IE/Safari solutions. So the legend is thrown out to the left. The best solution now would seem to be a basic line of code for Opera and Gecko, a negative margin for IE hidden behind a hack, and let Safari do whatever it wants. But more testing is needed.
uglegend as Gecko does. This is a problem as both Opera and Safari are under constant developement and have good CSS support. So how do we distinguish between them?