I can make the dynamic display block work using a custom content as below

Only local images are allowed.
Only local images are allowed.

It work OK in Firefox and IE7. However when testing in IE6, the initial image loading is correct. But as soon as the second image come in, the whole page will be shorten by the height of the image. You can see the problem if you use IE6 to visit my site at www2.igarment.net/drupal.

Any idea what was wrong?

Comments

geraldme’s picture

I was using custom content in the above post. The content of the custom content was

<div class="images">
  <img..../>
  <img..../>
</div>

and cycle on "img". Work for Firefox and IE7, but problem in IE6.

I then try to create a block and put the above code in the block. So the source of the ddblock is an instance. It work in IE6 too. So the above problem only limit to using custom content type.

BTW, I cannot modify the source of previous ddblock, it couldn't save. I need to create a new ddblock.

But I found another bug. Because of the test, I have create some ddblocks. Since using custom content doesn't work. I remove the problems ddblock, the content, and the content type. (In the order I type.) Now there is only one ddblock. But when I click "configuration" for some other block, one of the block will have all the extra ddblock fields in the block config page. And after clicking save, it will send me to the "ddblock" module configuration instead of returning to the admin/build/block page.

ppblaauw’s picture

Status: Active » Postponed (maintainer needs more info)

I can not test with IE 6.

As I understand you correct:

When you use a node from a content type and put the code:

<div class="images">
  <img..../>
  <img..../>
</div>

And use img as content-container is does not work in IE6

When you put the code in a block and then make a dynamic display block instance from this block it works in IE6.

-----------------
Second bug: Is this the same as in issue http://drupal.org/node/359810?

There is a patch for this

Please let me know if I understand the problem correct and if the patch solves the other issue.

ppblaauw’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Closing this issue, suppose poster solved the issue.