fredsa / gwt-dnd

Library providing easy to use mouse or touch based drag-and-drop capabilities to GWT
42 stars 41 forks source link

IE not fading selected items. #107

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What version of GWT are you using? 1.3.3? 1.4.60? Other?

GWT 2.0

What version of the gwt-dnd jar file or library file are you using?

3.0.0

What operating system(s) are you using? Windows? Linux? Mac?

Windows

Does the issue occur in web mode, hosted mode, both or don't know?

N/A

What browser(s) do you use? Firefox, IE, Safari, other?

IE

What is the browser version (if you know) from Help->About?

IE 6 7 and 8

What steps will reproduce the problem? Please attach sample code if you
can.
1. Select an item 
2. The opacity is not shown correctly

What is the expected output? What do you see instead?

The item should be faded slightly

Do you have a workaround?

yes.. the problem is in the following line in gwt-dnd.css

        filter: alpha(opacity \= 30);

there shouldn't be a '\' in there. To work around I add css to put a 
correct filter in.. .ie. 

.dragdrop-selected ,.dragdrop-dragging ,.dragdrop-proxy {filter: 
Alpha(Opacity=30) !important;;}

Original issue reported on code.google.com by thebenja...@gmail.com on 19 Mar 2010 at 11:37

GoogleCodeExporter commented 9 years ago
Thanks for reporting your issue.

It turns out the actual issue is slightly more subtle. The backslash escaping 
is 
correct, but IE8 doesn't parse the CSS correctly unless there's leading 
whitespace.

I've filed this issue with the details:
  http://code.google.com/p/google-web-toolkit/issues/detail?id=4810

I'm marking this issue as 'Invalid' since the problem is really in IE8 and IMO 
can 
best be worked around in ClientBundle's CSS compiler (CssResource).

In the short term you can drop this into a (non ClientBundle compiled) CSS 
resource 
in your app as a workaround:

.dragdrop-selected,.dragdrop-dragging,.dragdrop-proxy {
    filter: alpha(opacity \= 30);
    opacity: 0.3;
}

Once GWT has a fix for this, recompiling your app and removing that workaround 
should 
resolve the issue.

Original comment by fredsa@google.com on 1 Apr 2010 at 5:38