Opened 7 years ago

Closed 7 years ago

#1526 closed defect (fixed)

Media objects show through new div-based dialogs

Reported by: wymsy Owned by: gogo
Priority: normal Milestone:
Component: Xinha Core Version: trunk
Severity: normal Keywords:
Cc:

Description

If a new dialog overlaps a video or audio object, the object can show through the dialog. In the case of flash objects there is a workaround by setting wmode='opaque' or wmode='transparent', but the others (quicktime, windows media, etc.) have no such attribute. The only way I have found to avoid the problem is to set visibility to 'hidden' on every object in the show() function in XinhaDialog?.js, and make them visible again in hide(). This works, but a couple of issues come to mind:

  1. Should this be a configurable option, so that someone who only uses flash can keep the object visible in the background using wmode?
  1. Should we consider the special case where an object has already been set up as hidden, and not restore its visibility? This seems like a fringe case, but in theory it could happen. It would require devising a way to mark the already-hidden object. Is it worth the effort and overhead?

Comments solicited.

Change History (4)

comment:1 Changed 7 years ago by gogo

1: yes
2: yes

Are select fields also affected, I seem to remember?

Just set some property .dialog_hidden to the previous state of the object and use that to restore.

But is hiding enough, or is there a focus/click issue to?

comment:2 Changed 7 years ago by gogo

Wiki formatting got in the way...

Just set some property, .__dialog_hidden to the previous state of the object and use that to restore.

comment:3 Changed 7 years ago by wymsy

Select fields are already taken care of (for IE 6) in the constructor with an iframe behind the div, but that doesn't block objects. By making them invisible there is nothing to show through. I have not seen any focus or click problems. I'm pretty sure it is just a display issue.
Thanks for the comments. I was tempted to take the easy way out on (2), but I have to agree, it's better to do it right.

comment:4 Changed 7 years ago by wymsy

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.