This is kind of a strange problem and might be hard to reproduce, but it's easy for me to reproduce on my local install (views HEAD, updated as of now).
To recreate this, it seems that you can use pretty much any view you wish. As an example, create a view and add Node: Type as an argument. Then click on "Node: Type" to edit the options for the argument. If I'm using FF 2.0.0.14 (either windows or Mac) and I try to click the Update button, I can't because the button isn't clickable. Instead, when I click on that button the cursor line starts flashing to the left of where I've clicked (see attached screenshot). If I select Node as the validation option, then the checkboxes for that validation type appear. However, I'm not able to click any of the checkboxes, but am able to click the "Action to take if argument does not validate".
I don't get this problem using Safari on the mac or IE 6 or IE7.
As a point of information, I only notice this problem when the label for Validator: is on the right side but the actual select box is on the left side (as in the screenshot). If I resize my browser so that the two line up, this fixes the problem and I can then click the update button and/or check the check boxes. I typically keep my browser window pretty wide (~1500 pixels wide), and I've noticed that if I start with a smaller browser window (~1000 pixels wide) I don't get this problem in the first place.
I've noticed that when using firebug, the div element in which the validator sits seems to be very large. I've attached a screenshot of what firebug shows the borders of the div being. Maybe this is normal, but perhaps it's related to the cause of the problem.
| Comment | File | Size | Author |
|---|---|---|---|
| ff_validator_div.png | 42.71 KB | aclight | |
| ff_validator_stuck.png | 31.87 KB | aclight |
Comments
Comment #1
aclight commentedBy the way, I can reproduce this problem with only the core modules plus views, views UI, and devel. I'm using the stock Garland theme.
Turning off the devel module eliminates the problem. However, at a quick glance, it doesn't look like devel loads its own javascript. Is there any chance that the views js might somehow conflict with devel in a way that would cause this?
Comment #2
merlinofchaos commentedOh wow, that's really interesting. I have no idea, offhand, why devel.module would be involved in this, but that's something that has to be investigated. I don't know that devel.module uses much javascript beyond the theme developer stuff.
Comment #3
aclight commentedI also forgot to mention that I've seen this "stuck" behavior a few times on non-views pages (I couldn't click on the "Save" button). However, it wasn't very reproducible and thus I did not try to see if I got the same behavior with the views, views UI, and/or devel modules disabled.
I also do not have the theme developer module enabled. I do have krumo installed, but I don't think that's the culprit because I have set devel to not use krumo.
I know next to nothing about javascript, and I'm not a CSS/theming expert, so I can't really think of any additional steps to take to determine the cause. However, if you're not able to reproduce this on your own machine, please let me know if there's any more information I can provide that would help with debugging.
Comment #4
karens commentedJust reporting that I've had the same problem (using Windows XP with FF) but haven't had time to try to figure out exactly what combination of things might be causing it. It definitely seems to be a css issue -- it appears that in some situations a div is overlapping the submit button which is what is making it unclickable. I have the devel module enabled but haven't tried to see if I still have the problem without devel.
If I can figure anything more out, I'll post back.
Comment #5
merlinofchaos commentedI added a clear-block div that should prevent overlaps and *may* fix this. Please let me know if it did not.
Comment #6
aclight commentedThe clear-block div did seem to fix the problem where the Validator: label is not adjacent to the actual select box, but did not fix the problem with not being able to press the button and click on some other form items.
Comment #7
merlinofchaos commentedKarenS, do you also have krumo involved anywhere in this?
Comment #8
merlinofchaos commentedOk, I had themer extroardnaire Suzi look at this, and she was unable to duplicate this problem. I also am unable to duplicate it; the only real difference I can see is that I don't have krumo installed.
Comment #9
karens commentedNope, I'm not using krumo. I don't even know what that is :)
I'll see if I still have this problem and report back.
Comment #10
merlinofchaos commentedNot much more we can do until we can figure out a way to repro this.
Comment #11
karens commentedOK, I can still reproduce this with the latest code using FF on Windows XP, but only on certain screens. One is when I click the 'settings' button for a table view which results in not being able to click on the 'Update' button in the style options.
The devel module uses krumo, so I guess I am using it now, but wasn't when I first saw this. But I did find that I could get the page to behave correctly if I turn the devel module off, so the devel module seems to be involved in this somehow.
I tried using some of my web tools to outline css divs so I could see what was where, but when I add outlining to the page the buttons work right, so that didn't help.
I guess the work-around for now is to turn off the Devel module while editing Views.
If I notice anything else, I'll report back.
Marking it back to active so anyone else with other info can chime in.
Comment #12
aclight commentedFixing status.
Comment #13
karens commentedGetting this narrowed down. It is caused by the devel module's PHP block. I can have Devel turned on so long as that block is not enabled on the Views settings page and everything seems to work right. When I turn that block on, I get the mysterious unclickable buttons.
I'm not sure I can take this any further, but maybe someone else can figure it out from that.
Comment #14
aclight commentedInteresting--I am also using that block on my dev site (in the footer, for what that's worth). I'm not on my dev machine right now to confirm that turning off this block prevents the strange behavior, but this seems very plausible.
Comment #15
merlinofchaos commentedComment #16
merlinofchaos commentedComment #17
merlinofchaos commentedSorry about all the state changes.
Comment #18
esmerel commentedNo updates for more than 30+ days.
Comment #19
esmerel commented