Just installed View Reference (thank you very much danielb) and my first test view reference didn't display properly - the non-table elements would appear (header, more link) but not the table, which is the importnat bit.

After a few hours of mucking around I found the problem:
Table-style views with sticky headers won't display in a collapsed fieldset in PC IE.

No problem with Firefox, Chrome, Safari and Opera on PC (haven't tried Mac).

And no problem in IE for always-open fieldsets or collapsible fieldsets (starts open, user may then collapse it). The problem is limited to referenced views inside a collapsed fieldset (starts closed, user may expand it).

The problem disappears as soon as I uncheck the sticky header feature in the settings for a table style of formatting in the view.

I'm not a programmer so I have no idea why.

It's not a dealkiller for me right now - I can get by without the sticky headers - but it would be very nice to have this work for IE eventually.

My platform:
Windows XP SP2
xampp - localhost
Drupal 6.10
View Reference 6.x-2.13
Views 6.x-2.3
CCK 6.x-2.2

(Note to self: minimise variables next time you introduce a new module.)

Comments

danielb’s picture

danielb commented

Why are you displaying a view in a fieldset? I don't think this module provides that function. The reference itself works, which is the job of this module. You may need to theme your output yourself by overriding the field formatters, or perhaps the views templates, but I think this use case is too rare for it to be handled by default in this module. Which version of IE? If it's IE6, this is definitly something you should handle specifically for your site.

Matto’s picture

Matto commented

danielb - I'm displaying a view in a fieldset because it matches the presentation format of other fields on this particular node type.

And it always works except under the very specific conditions outlined in my issue post.

It's IE 7.0.5 and the theme is Garland.

So this is in no way a big deal and I'm not implying it's a shortcoming of your excellent module - and I don't expect anyone to spend time "fixing" it.

I just thought I might save other people some time by posting this limitation as a minor issue. If there was a "very minor" tag I would have chosen that. Maybe I should have chosen "feature request" rather than "bug report" - I'm new around here.

danielb’s picture

danielb commented
Status: Active » Closed (won't fix)

Sorry I don't think this is within the scope of this module. You are having problems with Drupal's compatibility with IE: http://drupal.org/node/335931
There are some suggestions on how to fix this there.

Matto’s picture

Matto commented

Yes, I see what you mean. Thanks.