It seems that there is more than one way to skin a cat. Ages ago I wrote about a mad IE duplicating text bug that would repeat bits of content lower down on the page. It had me scratching my head for a little while wondering how IE could be home to yet another bug, especially one this weird. My old friend Google came to the rescue in the end, showing me a cure.
Now though there appears to be a new and even simpler cure. The problem occurs when you have two floats, and comments between them. The solution I used previously was to remove the comments, but now it appears that another fix is simply to add display:inline to the css rule for the floats. I pretty much do that automatically now, to avoid IE doubling the margin around floats, so it fits right in, and means I can forget about removing comments from my code.
Labels: css
Jason posted this on Wednesday, February 20, 2008 at 9:55 am.
Read comments (1). Leave comment.
Browser inconsistencies are something that drives a sane web developer mad. For example, last week, I was trying to shoehorn a fairly simple-looking design into some html/css code, ready to be dynamicised (yes, I did just write dynamicised. Sorry.) Unfortunately, what happened, as always, was that Safari used a different line-height to everyone else, IE used a different heading size, and Firefox was absolutely perfect, because that’s what I was doing most of my testing with.
I come across this problem all the time, as you can probably imaging, and my solution is to have a base css file that I then modify and extend for every project. Doing that largely eliminates inconsistencies, or at least makes inconsistencies consistent project after project.
Eric Meyer’s ‘CSS reset’ stylesheet has been knocking around for some time, and is a useful resource to use or just to look at and understand why he’s done what he’s done. Anyway, he’s now given it a permanent home on his site, so there’s somewhere to check back for updates.
http://meyerweb.com/eric/tools/css/reset/
Here it is in full…
/* v1.0 | 20080212 */
html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, font, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td {
margin: 0;
padding: 0;
border: 0;
outline: 0;
font-size: 100%;
vertical-align: baseline;
background: transparent;
}
body {
line-height: 1;
}
ol, ul {
list-style: none;
}
blockquote, q {
quotes: none;
}
blockquote:before, blockquote:after,
q:before, q:after {
content: '';
content: none;
}
/* remember to define focus styles! */
:focus {
outline: 0;
}
/* remember to highlight inserts somehow! */
ins {
text-decoration: none;
}
del {
text-decoration: line-through;
}
/* tables still need 'cellspacing="0"' in the markup */
table {
border-collapse: collapse;
border-spacing: 0;
}
Labels: Code-bits, css
Jason posted this on Wednesday, February 13, 2008 at 4:17 pm.
Read comments (0). Leave comment.
Having just deployed the latest release of design agency Outburst’s website, I was again thinking about the order of source in html, and how I would put the content first in that site. I could use absolute positioning, but I don’t think that would work in cases where the font size had been increased by the user, or where the user’s display has a resolution greater than the default 96 dpi.
In a spare moment, I did a quick search and found an old but pretty informative presentation and article on exactly that, where they’d done a little bit of user testing. It’s so hard to find that kind of hard information I thought I’d pop a link up here.
http://www.usability.com.au/resources/ozewai2005/
Labels: Accessibility
Jason posted this on Tuesday, February 05, 2008 at 2:50 pm.
Read comments (0). Leave comment.
Most of the time, the people I deal with are decent individuals who just want to work and get their jobs done. Some of them are more than that: inspiring, charismatic, that extra bit of pleasure to work with. Sure, sometimes the wants of the client and the web developer don’t exactly match up, but usually these hurdles are fairly low and easily stepped over.
Now though, I come to the exception. The kind of person who’s like oil to your water. Like banana to your cod and chips. I’ve very occasionally encountered this type, and have found that although decent, honest and all the rest of it, for some reason they grate, irritate, depress, and suck you into a sullen grey world.
The big question though, is when I come upon someone who has this effect on me, how do I deal with him? I can’t answer that right now. I’m torn, between being a professional, and just working around the personal difference, and being a human, and not wanting to fill my life with stress and confusion. Thankfully, having dealt with one such person in the past, I’m able to draw a conclusion. It’s just not worth the anguish. Regretfully, of course, because who knows, I could miss out on a wonderful experience, a good contact and future work. But the risk — the risk! — when every fibre is telling me misery lies round the corner, the risk is too great to take.
Jason posted this on Friday, February 01, 2008 at 1:39 pm.
Read comments (0). Leave comment.
