Closed (cannot reproduce)
Project:
Collapse Text
Version:
6.x-2.0
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
18 Feb 2011 at 00:09 UTC
Updated:
16 Mar 2011 at 15:37 UTC
I have just installed the Collapse Text module to my website, and it looks Awesome. However, I have come across a very serious problem. When I sign in to the site using internet explorer(not the latest one, an old version found in school computers possibly ie6), there is a glitch. When I click on an expandable text, it expands but the text under it(which is also expandable) doesn't move down. Thus, there is an overlap of text. This is not a problem in the latest version of IE, Chrome, or Firefox. I really need to fix it so users using the old version of Internet Explorer don't encounter the glitch. Please help!
Comments
Comment #1
Darkestine commentedJust to clarify, ie8 and up looks fine. Anything below that, like ie7 and ie6 are the browsers where it just messes up.
Comment #2
pukku commentedHi!
First, could you try using the dev release? I've reworked a lot of it to make some things work better, and I'm wondering if any of the changes will have fixed it on your site.
Second, are you using nested [collapse] tags? If so, do un-nested ones work?
Third, are you using a default theme? Or a custom theme? If a custom theme, do you also use it for the administration theme, or do you use a default one for the admin theme?
Ricky
Comment #3
Darkestine commentedCould you please explain what you mean by nested/un-nested? I do write out [collapse] and [/collapse]. And yes, I do use a custom theme for both default and normal users. I installed the dev version, but the problem still insists on ie7. When I click on a collapsible text item, it drops down but another collapsible text that is under it does not move down as the original collapses.
Comment #4
pukku commentedHi!
By nested I was referring to using collapse tags within collapse tags.
Do you use your custom theme for administration as well? That is, if you're installing a new module, or editing a node?
The way the collapse_text module works is to hook into the way that Drupal does collapsing fieldsets. So in theory, if they work on other pages with your theme, they should work in collapsed text. There are a few tweaks on this though, and the IE browsers tend to be odd about such things.
I did just commit one change that *might* help; it's version 1.6.2.2, and the dev version should be updated within 12 hours with the new file. Or you can get it from CVS.
Ricky
Comment #5
Darkestine commentedOh, no I do not use collapse tags withing collapse tags. It looks like this:
A
i
ii
iii
B
i
ii
iii
C
i
ii
iii
And they are set to the uncollapsed form by default using [collapse collapsed]. All the objects inside A, B, and C are just links to other pages. In ie7, when I collapse one category, like A, C will go down allowing A(i, ii, iii) to expand. However, B will stay where it was, overlapping with A(i).
Comment #6
Darkestine commentedI just found something... First time I tried this, I just wrote my code like this:
A[collapse collapsed]
[/collapse]
B[collapse collapsed]
..........
I did that without hitting enter between the [/collapse] and [collapse collapsed]. Without the space in there, the block had an uncanny amount of space between each collapse tag. However, there were no glitches in ie7. Then, I went back in and hit enter between each [/collapse] and [collapse collapsed]. This got rid of all that unwanted space in between, but ie7 started glitching. I need to have tags without much space in between while not glitching in ie.
Comment #7
pukku commentedAre you using a graphical text editor (FCKEditor, TinyMCE, etc.)?
Comment #8
Darkestine commentedUmm...not that I know of. Just the default one drupal comes with.
Comment #9
pukku commentedSo, I'm not sure what is happening here; I did just post a new version though -- could you test that and see if it has the same problem?
Ricky
Comment #10
pukku commentedThis really sounds like a version with the theme -- all that this module does is use the built-in support for collapsible field-sets that comes with Drupal. Please test this with 6.x-2.1, which was just released, and might fix it -- it puts a form tag in a slightly different place, which might affect things?
I'm marking this as closed, unless you can confirm it's still a problem with the new version of the module.
Ricky