Opened 11 years ago

Closed 11 years ago

Last modified 7 years ago

#6945 closed defect (fixed)

BorderContainer: events seep through dijitSplitterCover in IE

Reported by: guest Owned by: Adam Peller
Priority: high Milestone: 1.2
Component: Dijit Version: 1.1.1
Keywords: Cc:
Blocked By: Blocking:

Description

In IE, events will seep through dijitSplitterCover. Temporary fix:

.dijitSplitterCover{ background: white; filter: alpha(opacity=1) }

This will trick IE into not seeping events through the SplitterCover?.

Attachments (1)

test_BorderContainer_full.html (1.5 KB) - added by guest 11 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 11 years ago by Adam Peller

Component: GeneralDijit
Milestone: 1.2
Owner: changed from anonymous to nonken

comment:2 Changed 11 years ago by bill

Can you be more specific? Are you talking about mouseOver events, like if you drag the splitter over a button? And is this for BorderContainer??

comment:3 in reply to:  2 Changed 11 years ago by guest

Replying to bill:

Can you be more specific? Are you talking about mouseOver events, like if you drag the splitter over a button? And is this for BorderContainer??

Yes, this bug is for BorderContainer?.

When _startDrag fires for a BorderContainer?, a covering div called dijitSplitterCover is placed over the area of the BorderContainer? so that events (mouseover, etc) from elements below do not interfere with the dragging of the slider.

However, in IE, even though the cover is placed over the elements below, events on those elements fire. This makes splitter dragging very choppy, especially when dragging over an iframe. Sometimes, the slider will get in a strange state where it is stuck on the mouse, and clicking will not release it.

I have attached an example.

Changed 11 years ago by guest

comment:4 Changed 11 years ago by guest

Oops, forgot to attach. Here is the file.

comment:5 Changed 11 years ago by bill

Summary: Events seep through dijitSplitterCover in IEBorderContainer: events seep through dijitSplitterCover in IE

OIC. OK, cool, thanks for the explanation, and the fix!

comment:6 in reply to:  5 Changed 11 years ago by guest

Replying to bill:

OIC. OK, cool, thanks for the explanation, and the fix!

Something to consider: Instead of fixing the bug in CSS using the proprietary "filter: alpha(opacity=0)", you could query dojo.isIE on _startDrag and programmatically apply the filter.

comment:7 Changed 11 years ago by Adam Peller

Owner: changed from nonken to Adam Peller
Status: newassigned

comment:8 Changed 11 years ago by Adam Peller

Resolution: fixed
Status: assignedclosed

(In [14185]) CSS hack to stop mouse events in IE and boost splitter performance. Fixes #6945.

comment:9 Changed 7 years ago by bill

In [30558]:

use opacity:0 rather than filter:... on IE9 and IE10, fixes #16679 and refs #6945 on trunk, !strict

comment:10 Changed 7 years ago by bill

In [30559]:

use opacity:0 rather than filter:... on IE9 and IE10, fixes #16679 and refs #6945 on 1.8 branch

comment:11 Changed 7 years ago by bill

In [30560]:

use opacity:0 rather than filter:... on IE9 and IE10, fixes #16679 and refs #6945 on 1.7 branch

Note: See TracTickets for help on using tickets.