Closed (fixed)
Project:
WYSIWYG image upload - Inline images for your WYSIWYG
Version:
6.x-2.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jul 2010 at 20:29 UTC
Updated:
31 Jul 2010 at 15:10 UTC
Comments
Comment #1
eugenmayer commentedWell that one is already know - no idea how to fix this though. could be a jquery_update bug or anything in between. Anybody has a slightly idea?
Comment #2
newmediaist commentedIt smells like a "weighting" issue - i.e. the WYSIWYG JS file is being loaded too early in IE7 when JS compression is on. As far as I know, it is not possible to set "weights" of JS files in Drupal 6 though?
Comment #3
eugenmayer commentedWell how could a browser influence what the backend aggregates? Thats impossible.
Comment #4
newmediaist commentedWhat I am suggesting is it seems that IE is reading the aggregating file in a different method than Chrome/Firefox - which leads me to believe maybe chrome fire fox reads the whole aggregated file before trying to interpret the javascript, while IE interprets it chronologically as it loads
hence maybe the WYSIWYG Image Upload script is "too early" in the file for IE
Just a shot in the dark!
Comment #5
eugenmayer commentedHmm, well they all read it serialy. I think your thoughts are not in the wrong direction. What i suggest is that the IE is pretty sensible what is about the JS syntax. And i could think that some strange newline or braces are braking it.
how i hat those bugs...
Comment #6
newmediaist commentedUpgrading to the newest DEV release of WYSIWYG seems to correct this issue by preventing the editor's JS file from being aggregated - seems to work fine in IE now w/ JS compression turned on.
Comment #7
eugenmayer commentedOk so this seems to be an issue with WYSIWYG? Thank you very much, i will add this to the incompatibilities section!
Comment #8
newmediaist commentedCorrect - I believe upgrading to the newest DEV of WYSIWYG corrected this issue.