Need to support setting wmode paramater to avoid flash / Javascript z-index issues
| Project: | SWFObject API |
| Version: | 6.x-1.0-beta1 |
| Component: | Code |
| Category: | feature request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Many users are finding that superfish menus, suckerfish menus, Lightbox2 and other Javascript graphics elements are having a hard time with embedded flash in drupal. The solution has been found but requires changes to all flash embedded in drupal. The wmode paramater must be set as a param and as a flash var to opaque mode so that the flash will surrender its topmost position (which is the cause of the obscuring of other z-index placed objects in drupal.) Making this pramater configurable in your module would go a long way towards solving the problem since many of drupals flash elements are displayed by way of your module. I tried to hack this data into the code but this is not my forte. I belive this is an issue for all flash related modules, and needs to be addressed by those with the most use first. It cannot be solved by developers on the javascript fromt, only on the embeding of flash front.
#1
Well, when building the swfobject display, you can pass wmode and flashvar arguments. Are you having a problem passing these arguments?
#2
perhaps I am just confused, I use the Views Charts module. It uses this module to embed the graph. Short of hacking code, I cant see how a user can pass the wmode var. Further, this is not a 1 time thing. it should be set on every one every time. I am fond of suckerfish and superfish menus as well as the admin menu module. My Charts and flash slide shows always conflict with JavaScript based graphics and flash always wins the top spot in the z-position food chain obscuring the menus or other JS elements. Other modules have this trouble and I have had to hack the wmode into the embed code as opaque to correct this behavior. this appears to be something left un-addressed in most flash modules in drupal. I dont think a user should be expected to hack a flash parameter into some module code to achieve this, I also believe, though I may be wrong, that an admin config dropdown for setting the wmode parameter to one of its 3 possible values is something everyone will need. Am I out to lunch here?
#3
Did anyone find a solution to this issue?