In this question, OP says he can't trigger
onclick events when
float is used. It turns out that another element was blocking the intended click targets, and when moved, the problem disappeared.
This question follows a common pattern: "I have a problem, but commenters say it works fine; the solution is something silly that I didn't catch."
Someone searching for reasons
onclick won't fire will not find this post helpful. I suggest a community-available flag for asker-specific problems that have nothing to do with the code itself - call it the "naiveté" flag.
Countercounterargument: It doesn't serve quite the same purpose as "too specific", since it doesn't have to do with provided code at all.