[drupal-devel] [bug] Konqueror 3.3.x problems with forms input inside fieldset tags

[Steven]

Issue status update for http://drupal.org/node/16729

 Project:      Drupal
 Version:      4.5.2
 Component:    node system
 Category:     bug reports
 Priority:     normal
 Assigned to:  Anonymous
 Reported by:  syscrusher
 Updated by:   Steven
 Status:       active

I believe that piece of CSS is there for IE5, but I can't remember if it
was for Windows or Mac. I'll do some testing later.


Steven



Previous comments:
------------------------------------------------------------------------

February 4, 2005 - 06:33 : syscrusher

Certain versions of the Konqueror browser have a serious problem with
form input in Drupal 4.4.x and 4.5.x. The symptoms are that keyboard
and mouse input is completely ignored in the affected "text" and
"textarea" fields. The symptoms only occur on textual fields that occur
within a <fieldset>...</fieldset> tag set. This occurs, for example,
when the form_group() API function is invoked.

I have tested several variants on the fieldset attributes, and as far
as I can tell it doesn't matter what attributes are applied. I also
tried it with a manually-created <fieldset><input type="text" ...
/></fieldset> sequence, to eliminate the subtags such as legend,
description, and title. The problem occurs even with a bare fieldset,
and immediately goes away when the form elements are used without being
in a fieldset. I further tested to ensure that the <table> tag was not
involved, because a Google search suggested that there were problems
with tables and fieldsets in Konqueror. Again, the problem is
duplicable with no table in the fieldset.

It took a lot of digging, but I have finally traced the problem to the
file misc/drupal.css. Specifically, the following clause appears to be
at fault:
.node-form fieldset {
      display: inline;
}

If I comment out the "display: inline;" attribute, then the fields work
correctly. There does not appear to be any ill effect from this so far,
but I haven't tested extensively nor have I tested to see if this patch
breaks any other browsers.

I can duplicate this problem across several patch levels of Konqueror
3.3.0, and across Drupal 4.5.0 through 4.5.2.


------------------------------------------------------------------------

February 4, 2005 - 07:14 : syscrusher

I've verified that the patch doesn't break Firefox 1.0, and also that it
/does/ fix the problem with Konqueror 3.3.0 in Drupal 4.4, on one of my
production sites. Incidentally, the problem doesn't occur with older
Konqueror versions, as far as I can tell.