31 March 2010 at 9:07am
I have tried and pretty much successfully nested a ImageDOM inside a normal DOM. My issue here is in Internet Explorer the formatting is way off and I cannot get this fixed. I have even tried modifying the plugin's CSS files, and Template .ss files. I will attach a screenshot in a reply below so you can see how it looks.
1. I have no slider to size the images (admin)
2. They all float too far left with no padding/margin.
3. the bottom bar of the DOM sits over the delete (trashcan) like it wasn't 'cleared' of the above floats.
Webpage error details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
Timestamp: Tue, 30 Mar 2010 20:04:55 UTC
2 April 2010 at 9:58am
I completely redid the installation, and installed the version off the 2.3 Branch and I still have the same problems.
I've also noticed SimpleHTMLEditorField doesn't play nice in IE 7 or 8. I can't get the formatting to work for Lists. Firefox is just fine on windows...just not IE and my client is an IE only user. He was trying to add a unordered list and couldn't get more than one with a bullet. I tested it...and it's like IE is treating the content as a <p> and then wrapping the <li> around the <p> so if you are typing into the bullet, and you hit enter (or next line), and in IEs case, it's replacing that with a <br> it will still be in the first <li>...and any subsequest is the same.
28 August 2010 at 2:47am
Maybe a little late...But:
In your third post you said:
"The only other issue I see in IE is the pop-up inside the pop-up to edit the individual files loaded will load in the same (face)box and not in it's own overlay...can anyone else confirm this?"
I had the same problem. A client came up with it. I always use Firefox so I never saw it before. The problem is dataobject_manager.js line 38. Instead of "top" it has to be "var top" otherwise IE does not understand it. (whats new?? :D)
For me it fixed the problem. The nested DOM (or ImageDOM) opened in a new pop-up.