horizontal scollbar appearing every time
| Project: | FCKeditor - WYSIWYG HTML editor |
| Version: | 6.x-1.3 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Even in an empty box, the textarea is made wider than the visible size.
In other words, I can see something like 60 characters, but it looks like the cols parameter is set to 90 instead. This forces the browser to add a scrollbar at the bottom. Very annoying since the text just cannot be read without scrolling like crazy left and right all the time.
From all the searching and reading I have made I found nothing about a way to properly control that feature other than some elusive CSS modifications that so far have done nothing to me (which does not come as a surprise to me--but it could also be that I did not apply them in the correct files...)
The FCKeditor otherwise works well. It appears at the right place and behaves properly.
Note: does not work in SeaMonkey, FireFox and IE7. And probably others.
I use my own template and that could be part of the problem. But I have to use that template... Yet, if that's the case, then there should be an easy fix in one of the CSS files to make it work.
If anyone can help, it will be really appreciated!
Thank you.
Alexis Wilke
| Attachment | Size |
|---|---|
| scrollbar.png | 67.02 KB |
#1
You wrote that you're using your own template, could you check does it also happen in Garland theme?
#2
Hi wwalc,
No it does not happen in Garland.
I create yet another theme with just CSS and it does not happen. So I really suspect that the tables are doing it. I'm wondering how you get the width for the tag within your IFRAME. It is very difficult to debug because I cannot use the right mouse button at all. I tried to turn it off, which "works", that is the contact menu is gone, but it still prevents the standard Browser menu from appearing. I tried with different keys and in SeaMonkey, Firefox.
So, I was thinking to try with CSS and see what happens. At least that would tell us whether it is the tags.
Thank you.
#3
I suppose I should change the status too when I answered... 8-)
#4
Hi guys,
Okay, two things on this issue:
1) The problem when using tables has never been solved. So there is most certainly an issue with that. Also, it does not matter to me anymore since I just won't use tables.
2) I ran in a small problem with using only CSS because I wanted the screen to have a minimum width. I put that in my body style declaration as in:
body { min-width: 1000px; }And that also generated the horizontal scrollbar. Once I moved that min-width declaration from the body tag to the very first <div> tag in the block, it worked just fine.
Now, it is up to you whether you want to be supported within tables or not, I guess...
#5
Can you point me to a sample theme where I could check it?
#6
Sorry for the little delay.
Although I fixed my customer's website with a fluid CSS templates, FCKeditor is still not working properly in the old table based version of the site. This can be found here:
http://alexis.m2osw.com/fckeditor
In order to test, go to:
http://alexis.m2osw.com/fckeditor/user
And login as FCK with top-secret password fckeditor911
Go to back to the Home page and click Edit.
There you see the FCKeditor in the IFRAME and somehow that the inside textarea appears wider than the IFRAME.
Let me know if you need/want the code of that site (i.e. theme)
I could also update the code since it is running with an older version, but I'd be surprised that the newest would fix this specific problem.
Thank you.
Alexis Wilke
#7
FWIW, I have the same problem on my site using a customized version of the NewsFlash theme. Works fine in IE, but horizontal scrollbar in Firefox 3.0.7. The theme does not use tables. I'll write again if I'm able to pin anything down.
#8
Ok, I should have read more closely above. Just as AlexisWilke mentions above, the problem was a min-width style applied to body in one of my stylesheets. This, of course, applied a min-width to the body in the iframe. It may be worth forcing a style override within the module stylesheets.
#9
Closing because of inactivity.