I was going round and round trying to figure out why Firefox would correctly show a 1px gray border on an “a” HTML tag where Internet Explorer wouldn’t. Turns out, I had used “grey” instead of “gray”. FF accepted it, IE didn’t. Lesson learned. But I spent hours trying to figure out what was wrong so hopefully someone else out there will save some time from this.
Tags
adsense animation apache apple auto future date blog coding compsci css diy flash forum game hard drive internet explorer iphone itunes java javascript link linux mac mysql netbeans Photography photoshop php plugin Programming proofbuddy prototype python reliti robot robotics scratch teaching theme tips twitter usb video web design wordpress youtubePopular This Week
- Difference in Hub, Switch, Bridge, & Router
- JavaScript Error ‘expected identifier, string or number’ in IE
- How to get a screen shot from an iPhone
- Multiple cases for switch construct
- PHP: A function to return the first n words from a string
- DIY: Make Your Own Ethernet Loopback Cable
- Chrome not saving cPanel password since upgrade
- Datatables jQuery plugin – Refresh table
- How to revive a dead Western Digital MyBook
- A routine to create GUIDs in PHP
My Other Sites
Ryan-
Funny. I’ve been using ‘grey’ for so long I can’t remember. I’ve always thought it was a more ‘proper’ spelling. Not sure why. Perhaps it’s my designer background.
Some CSS shorthand for ‘grey’:
border: 1px solid #ccc;
(no need to write out the full hex if there is a repeating pattern [i.e.: #999999 becomes #999; #3366cc becomes #36c;]) — but you probably already knew that)
On an unrelated note, it sounds like a dilemma I am now facing is one you’ve already conquered. A post from you in the Javascript forum of webmasterworld from February 18, 2005 read:
“I have series of div’s that all contain a single checkbox each. What I’m trying to do is to allow the user to click on the div it swaps the value of the checkbox. I’ve got this working, with one flaw. If the user clicks on the checkbox, it doesn’t swap. I understand why, it has to do with fact that clicking on the checkbox also fires the onClick of the div. Is there a good way to handle this so it works?
I’m thinking the easiest would be if I can get the name of the control clicked – something like if checkbox was clicked don’t worry about the swap b/c the checkbox takes care of itself, but if the div was clicked then swap it. But, since the div onClick fires either way, that’s causing a problem.
Thanks,
- Ryan ”
I am currently working with an image nested inside a element. Both have onclick events set. Clicking on the (nested) fires both onclick events — but I only want it to fire the one for the , not the one for the . I’ve tried cancelBubble (IE) and stopPropagation (Moz), but no such luck. Either my logic is off (most likely) or I just don’t understand the concept. Since it seems that you solved your situation with the nested checkboxes, I was hoping you could shed some light on how you did it.
Thanks for any help you can provide.
-Bob
Mine was actually a little different. I had a checkbox with its label wrapped in a div. Clicking on that div needed to set / unset the checkbox. It works if the user clicks on the div, but if the user clicks the checkbox it doesn’t do anything. Well, it actually sets and unsets the checkbox.
I’m still working on a solution :-)
I encountered the same problem. ‘grey’ is OK for firefox and chrome, but not for IE7.