This problems appears when Drupal has a longer (in my case 6+) list of terms to suggest for free tagging:
Expected behaviour: you start typing tags into the free tagging field in a node and get a list of suggestions from the tags already on the system. You choose one and continue tagging.
Actual behaviour: if the list of suggested tags is long enough to overlap with the body field of the node below, all the tags overlapping the body field are very hard to read (if there is text in the body field) and only those terms that do not overlap can actually be selected (this problem also appears when the body field is empty).
See the attached screenshot.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | body_field_tagging_0.png | 14.22 KB | Anonymous (not verified) |
Comments
Comment #1
Anonymous (not verified) commentedAnd here is the screenshot.
Comment #2
webchickWhat browser/theme/etc? This doesn't happen on my local install.
Comment #3
Anonymous (not verified) commentedExcellent point! It never occurred to me that this may be browser related - and it is. No problems with Opera (9.20) and Internet Explorer (7), but with Firefox (2.0.0.6); all under Windows XP. I use a modified version of pushbotton, but did not change anything even remotely related to forms.
Comment #4
Anonymous (not verified) commentedExcellent point! It never occurred to me that this may be browser related - and it is. No problems with Opera (9.20) and Internet Explorer (7), but with Firefox (2.0.0.6); all under Windows XP. I use a modified version of pushbotton, but did not change anything even remotely related to forms. Plus I do have the same problem with an unmodified Garland.
Comment #5
kiran_lakhotia commentedhi,
this bug only happens when the "suggest" list is inside a fieldset, and if the list overlaps with another textarea. In the system/system.css file, line 335 you have
This causes an "incorrect" behaviour in Firefox (v. 2.0.0.12). Removing this property resolves the bug, and also works on IE7 under winXP. Now this property was obviously added for a reason, and I'm not a css expert, so please suggest a preferred workaround for this.
I could not (yet) find any other css property which influences the behaviour. Is the above really the root cause?
Comment #6
dpearcefl commentedConsidering the time elapsed between now and the last comment plus the fact that D5 is no longer supported, I am closing this ticket.