vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB3 Programming Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=15)
-   -   Ajax Select Boxes (https://vborg.vbsupport.ru/showthread.php?t=119251)

amykhar 06-21-2006 06:31 PM

I have never banned anybody from vbulletin.org. I doubt you'd be my first choice. But that is off topic and I know you don't like off topic posts; so I'll shut up now :D

ok. off to figure out what I want to do to work around this.

noppid 06-21-2006 06:35 PM

Quote:

Originally Posted by tgreer
Of course I think you're nuts, amy - but I sense a ban hovering over my head if I continue. :)

They won't let me admin here, you're safe.

Actually, this is a great thread. I'm sorry for busting on Amy.

Princeton 06-21-2006 06:48 PM

place the "select" in a layer and hide the layer when you display the menu

tgreer 06-21-2006 06:57 PM

A "layer" is a deprecated Netscape-only element that will be cause validation errors with most DOCTYPES. The DOM version of a "layer" is a DIV, and DIVs are not exempt from the "IE select z-index" error.

The principle is sound, though, and that's why I think I ended up with putting my selects in an IFRAME for one particular project. Looking at amy's screenshots, I don't think that will work in her case, though.

Princeton 06-21-2006 07:05 PM

that's what I meant ... yes, it does work

we are merely changing the display to "none"

tgreer 06-21-2006 07:17 PM

Ah. In that case, you probably wouldn't even need the DIV, you could toggle the CSS "display" on the TD element holding the SELECT. In fact, you could probably toggle it on the SELECT itself.

There could be rendering problems with "display: none". I'd suggest instead, toggling "visible: hidden/visible".

Princeton 06-21-2006 07:18 PM

correct :D

I suggest testing on the platform that will be used (intranet).

amykhar 06-21-2006 07:20 PM

The iframe trick seemed to work, (thank you) but I'm willing to try toggling the visible and invisible property too because that would probably be easier with all the stupid form elements I have to deal with.

Of course, when I pass this off to the stylist, I'm going to have to explain why that has to stay there, but that shouldn't be too difficult.


All times are GMT. The time now is 02:14 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01618 seconds
  • Memory Usage 1,725KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (1)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (8)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete