I have two formatting problems that may or may not stem from the same yet unknown reason.
First: In Safari 3.04 there is a standard select box that appears over the HS pop up. (see attached graphic) Funny thing is that immediately after booting Safari the box is not there - then when i reload or submit it shows up again. Clearing the cache has no effect - only quitting safari & rebooting.
Second: With HS enabled, my second filter (non HS) is pushed down to the next row - and the nesting of tags seems to be a bit wonky. (see attached graphic)
Any ideas what might be goin on or how to troubleshoot?
Many Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| HS-exposed-filter-problem.jpg | 89.85 KB | Hunabku |
Comments
Comment #1
wim leersFirst: very strange. I can't reproduce this: I use Safari 3.04 myself. Are you sure you're using RC4?
Second: that's by design. Otherwise the other exposed filters would be moving around whole the time (because the hierarchical select expands and collapses).
Comment #2
Hunabku commentedYeh i know its weird - the safari glitch - seems like a client side thing but i am traveling now and don't have access to a different mac to test it. If your up for seeing if it happens on your browser i can send you the URL. PS - yes i'm using rc4
As far as the second item of HS pushing the next filter to a separate line - thats understandable that you would have it do that. My actual problem with this is that I'd like to put a thin column of help text the the "left" of the HS pop ups but try as i may (with divs and table cells) no luck. Seems like the tags being sent by HS are creating a tag nesting violation or something.
Comment #3
wim leersFirst: please send me that URL.
Second: in that case, use the #description property of a form item for the help text. If that's not sufficient, then comment everything in modules/views.js and modify the exposed filters table yourself.
Comment #4
wim leersHunabku sent me the URL and I could confirm the problem. It only occurred in the current Safari 3 (3.04) though: it worked fine in a Webkit nightly of a few weeks ago.
I reproduced this on my test site too now. However, it seems to happen *randomly*! I tried various tricks, none of which worked. Eventually I tried removing the context from the original select selector. And that made it work again for Safari 3…
This work-around should be removed when Safari 3 is updated.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.