Quite right. I'm afraid I didn't put the question very well. All I was trying to get at was an idea of whether it was worth putting in the work to fix any Opera idiosyncracies, if there still are any.
That said, my guess would be that while the aim is to code in a standards-compliant way, *in practice* what tends to happen (for me, anyway) is that I *think* I'm coding to standards, but I'm actually doing a running check on my work by testing in Safari and Firefox.
So the purist in me says, code to standards, but being a visual person first (designer) I rely on the visual for confirmation that I'm on the right track. Not quite kosher, I guess, but that's my admission for the day.
-Hugh
I don't mean to jump on this comment, so apologies if take out of context,
but the aim is to code for standards first, then deal with individual
browser issues as they come up. We should not need to "code for Opera".
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
