Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
javascript
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Sep 2007 at 18:46 UTC
Updated:
26 Sep 2007 at 11:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
ChrisKennedy commentedRenaming a variable (.height -> .savedHeight) in misc/tableheader.js fixes the bug.
Comment #2
anders.fajerson commentedNo more error on /admin/build/module in IE7.
Comment #3
gábor hojtsyWhat about the other alert?
Comment #4
jrabeemer commentedThis needs to get in before beta!
Comment #5
bdragon commentedThen beta breaker it!
Comment #6
gábor hojtsyAs far as I see, this fixes one of the reported two alerts. Therefore I asked: what about the other alert?
Comment #7
jrabeemer commentedThis patch DOES NOT fix the "/user/XXXX/edit" issue. In order to recreate, you must enable more than one theme and also give change theme permission to the user! The "Theme Configuration" will only appear there if you set those conditions.
Comment #8
ChrisKennedy commentedThis fixes both alerts, which are due to same bug. If you are testing this patch, remember to turn off JS aggregation and do a hard-reload after you apply it to load the updated js file.
If the alert still exists, please let me know how you are getting it.
Comment #9
anders.fajerson commentedYep, fixes the error on /user/XXX/edit (collapse theme configuration) as well.
Comment #10
jrabeemer commentedOk. I'll test again. FYI, http://drupal.org/node/174708 adds jQuery 1.2 which will probably break this patch. :-/
Comment #11
ChrisKennedy commentedTo elaborate: the error occurs wherever there is a collapsible fieldset with a table inside it that has a header. There is only a single bug: the two pages listed happen to have this combination of form elements. The bug would also occur in any contributed module or other core module where this happens.
Comment #12
jrabeemer commentedI dumped all my previous patches and updated to CVS and patched to this. It works! Ready to go!
Comment #13
ChrisKennedy commentedRegarding #10: no. It does not break this patch, nor does it fix this issue.
Comment #14
gábor hojtsyHappy to hear about the tests! Thanks a lot, committed.
Comment #15
(not verified) commented