if you put a textarea in a collapsed fieldset and view the form on safari, when you expand the fieldset, the text area is missing. i tried in both garland and bluebeach, and it's broken in both places, so i know this one isn't garland-specific. i tried in FF and it works. attached is a patch (in progress) against the user settings page that's where i noticed the bug. again, the key thing is that the fieldset starts off collapsed on page load. if you have a collapsible but non-collapsed fieldset, the text area works fine.

screenshots coming next...

CommentFileSizeAuthor
#2 ff_collapsed_textarea.png99.91 KBdww
#1 safari_collapsed_textarea.png72.08 KBdww
safari_collapsed_textarea_example.patch.txt8.5 KBdww

Comments

dww’s picture

dww
we/he/they
commented
StatusFileSize
new safari_collapsed_textarea.png72.08 KB

safari, after expanding a collapsed fieldset... notice "Body" has a title and description, but no actual text area. :(

dww’s picture

dww
we/he/they
commented
StatusFileSize
new ff_collapsed_textarea.png99.91 KB

firefox, after expanding the same fieldset... works as expected.

Steven’s picture

Steven commented

I'm pretty sure this is because that form is nesting fieldsets, something which has always been discouraged. In any case, the JS needs to be patched, not the form.

Nick Lewis’s picture

Nick Lewis commented
Status: Active » Postponed (maintainer needs more info)

Almost certain that this is a safari 2 bug (that's usually version number 4xx in analytics, safari 3 is 523.xx -- the numbers come from the webkit version...). At my own blog, Safari 2 is somewhere around 3 percent of visitors.

Can anyone still reproduce this on safari 2? (all the macs I have access to have safari 3 installed, and our attempts to install dev versions of 2 just result in the browser crashing).

Do we care about safari 2? It has "its own way" of dealing with form elements -- and I believe has its own expandable textarea grippy by default on textareas.

If we do care about safari 2, someone should at least verify that this bug still exists. It has the ability to make textareas unusable to 3% after all. If its still there, we can simply use the jQuery.browser object to detect safari 2 (i think), and prevent the script from running.

dww’s picture

dww
we/he/they
commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

I was afraid when Apple's software update told me it was going to blast my copy of safari with safari 3, so I copied my 2.0.4 binary out of harms way before I ran the upgrade. ;) So, now I've got both working nicely on my machine, for testing stuff like this (and at times when I hit Safari 3 bugs that are so annoying I'd rather just use Safari 2 for something).

Anyway, I just tried with the latest HEAD version of core on a clean install, using both versions of safari, and I can no longer reproduce the bug. Presumably, the newer version of jQuery now in core works around the browser bug(s).

Thanks for asking. ;)
-Derek