If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Z-Index and Safari

I have a Div that pops up and is closed with an X in the corner. This closes in Explorer, Chrome but not in Safari, I beleive it is the z-Index causing this. How would I make this work in all browsers?

The advanced editor (activated by using the 'Go Advanced' button from the simple editor) has buttons for PHP, HTML, and CODE braces. But for simplicity, you can just use the [code][/code] tag for any code if you prefer.

Your applicable post(s) in this thread have already been edited for you by a member of the moderator staff.

Also, please do not hot link to your pages. Give a text only link like (without http:// or www.):

schuremediagroup.com

or do:

[noparse]www.schuremediagroup.com[/noparse]

so it will look like:

www.schuremediagroup.com

Oh, and I loaded the page in Safari/Win and it worked fine. I guess you mean on a MAC, or a mobile? What device(s) are you seeing this problem in Safari on?

Last edited by jscheuer1; 09-23-2013 at 05:34 PM.
Reason: looked at the page, add info

Is that where clicking (I guess tapping) on the formatting buttons causes a problem as well? They use a non-standard method to accomplish their objectives, perhaps that's not to those device's liking.

I have an idea about what you're asking about. It might not be the z-index at all. I would need to see the javascript that's used to assign the close event to the div. But I have seen where on those devices, a click is not always registered when a tap occurs, especially on something that's not a link or button. You may have to assign a touchstart event to the div.

I'll poke around and see if I can find the javascript. But if you know where it is, please tell me.

The browser cache may need to be cleared and/or the page refreshed to see changes.

Hopefully that will not adversely affect anything else. Browsers without touch will ignore it, as will older browsers (IE 8 and less) that don't have addEventListener. Android might do a double close, but I added a stop() to the animation to prevent that.

I checked that it has no syntax errors in Chrome's console, but I have no iPad, or iPhone to test on. The same principle works in a menu script I updated recently.