Closed (fixed)
Project:
Web File Manager
Version:
5.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Apr 2007 at 20:46 UTC
Updated:
16 Jun 2007 at 13:17 UTC
I've attached a screenshot which demonstrate that the CSS layout is broken in IE7 (probably 6 too but I couldn't test that).
It goes all wonky:
Let's see, what else might help you?
I wouldn't concern myself with it except that some of my contributors whom I trust to post on my site use IE. I was hoping to switch them over to webfm this week.
Comments
Comment #1
robmilne commentedThis is an ongoing issue with ie. The module was originally developed to be an admin module where I had some influence over the client's choice of browser. Since I wrote everything from the ground up in javascript without a framework (ie: prototype or jquery) there are cross-browser incompatibilites. I have improved the menuing recently in ie (with the help of Ryan Showers) but the drag and drop is still hopeless. If anyone wants to volunteer some assistance here I'd be very grateful.
Comment #2
andremolnar commentedRob,
I think it might be a good idea to have a javascript warning for IE until this is resolved. Thoughts?
e.g. "You are using a hopelessly broken browser that is the bane of all developers' lives. Internet Explorer breaks the internet and this module. Please use FF until WebFM version 2.x coming soon" ;-)
andre
Comment #3
tcblack commentedPerhaps there is there a way to hook into IE Destroyer?
It looks like a bit of code needs to be inserted into the template file after body so I might try to find a way to use IE destroyer wherever this module is called? At least on the main webfm page.
Comment #4
robmilne commentedI'll look into a notice wrt IE. Probably a gentle nudge since I'm not interested in starting a flame war with MS devotees.
Comment #5
robmilne commentedThe latest dev snapshot (May 31+) has IE drag and drop fixes. Still a few minor cosmetic issues but it works finally.
Comment #6
jraper@groups.drupal.org commentedI see this same broken behavior in the 4.7 version of Web File Manager. Can we get that version of the Module updated with theses same fixes?
Comment #7
(not verified) commented