Hi,
I posted this to the support list, but given the topic, I thought maybe this was a more appropriate list.
I've run into a strange problem where the autocomplete drop-down for freetagging on node/add/foo is actually behind the rest of the page elements. In other words, the form labels and fields are on top of the drop-down display. If the fields are opaque, then the drop-down disappears behind the body textarea.
I'm not a js adept. I'm trying to figure if the drop-down has css class or id designations I can use to do something like bump the z- index -- or something! I tried to discern what's in the autocomplete javascript, and guessed at an autocomplete class, but adding .autocomplete stylings to the style.css file hasn't seemed to provided any solutions.
Thanks.
Laura Drupal 4.7RC2 Custom phpTemplate theme
Laura Scott President laura@pingv.com
pingVision, LLC 4450 Arapahoe Ave, Suite 100 Boulder, CO 80303 www.pingv.com 303.415.2559
On 19/04/06, Laura Scott laura@pingv.com wrote:
guessed at an autocomplete class, but adding .autocomplete stylings to the style.css file hasn't seemed to provided any solutions.
You can style the autocomplete popup with #autocomplete. Some styles are already applied in drupal.css.
-- David Carrington
On Apr 20, 2006, at 2:35 AM, David Carrington wrote:
On 19/04/06, Laura Scott laura@pingv.com wrote:
guessed at an autocomplete class, but adding .autocomplete stylings to the style.css file hasn't seemed to provided any solutions.
You can style the autocomplete popup with #autocomplete. Some styles are already applied in drupal.css.
[cross-posting from the support list]
FWIW, here's what I did to solve the problem:
As an experiment, I edited the drupal.css file to add a z-index on #autocomplete, and it fixed the problem. Well, that's not optimal as then I'd be re-editing that file with every update. Then I realized what I was doing wrong: I had added a position: relative to style.css (because afaik position is required for z-index settings), but drupal.css has position: absolute, and that was good enough for me. I deleted the override in the theme, and now autocomplete is working.
So it was my own mistake. Thanks for the response!
Laura
Op donderdag 20 april 2006 16:57, schreef Laura Scott:
As an experiment, I edited the drupal.css file to add a z-index on #autocomplete, and it fixed the problem. Well, that's not optimal as then I'd be re-editing that file with every update. Then I realized what I was doing wrong: I had added a position: relative to style.css (because afaik position is required for z-index settings), but drupal.css has position: absolute, and that was good enough for me. I deleted the override in the theme, and now autocomplete is working.
In future, however, we really want this to become transparant and Very Themable.
look at http://rubyonrailsblog.com/ vs. http://www.developonrails.nl/
Both use the *exact* same engines/code/whatever but one has its search-auto float in from the top (unnesssary blingbling if you ask me) while the other has it somewhere in his sidebar (far too hidden away to be usavle if you ask me). Both use the same code (typo: http://www.typosphere.org/) but still both manage to get a different look+feel for this particular.
Which route Drupal takes is, is not a point here. But the result should be, in this particular point, that AJAXy stuff is fully configurable and so in the theme level. That goes far beyond some #ids and CSS lines!
-
Bèr Kessels -
David Carrington -
Laura Scott