This is going to probably sound really silly but at this point I am dumbfounded as to how to add a border to the content area of FCKeditor.

I've set the WYSIWYG settings to use a custom css path. I know it is loading the file properly because it is using my body style from the css file.

To add a border to the content area (the area where you type), the following have failed for me:
- Added style for '#xEditingArea' to css file, it works when viewing fckeditor.html on its own but not on drupal form.
- Added style for just 'table' or 'td', once again it worked when viewing fckeditor.html on its own but not on drupal form.
- Added border to 'body'. This shows results on the drupal form, however the body was not taking up the full height, adding "height: 100%" caused other issues.
- Added wrapping div in fckeditor.html and added style for div in css file. This also did not work.
- Attempted to find what was giving the fckeditor's iframe the inline border style so I could delete it (was unsuccessful, fckeditor.js does not add inline styles to the iframe, something else is doing it).
- Tried changing the FCKeditors settings to use its default skin (noticed the default skin css had a border color of #ffffff, so I changed it), still no border.
- Tried changing my sites theme, this did not change anything.

Has anyone else had this problem?

Comments

TPerkins’s picture

TPerkins commented

Alright so adding a border inline style to a newly added div wrapper in the fckeditor.html had the intended result. It feels like a hack, but I will keep it for now.

I know this probably wasn't the right place to make a ticket, but I was about to pull my hair out.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

I suggest you give the Firebug extension for Firefox a try. It'll be able to tell you exactly which style rules, and from which files, are used by an element. Inlined styles added by scripts are of course harder to trace the source of, but at least you'll be able to identify exactly which styles are being applied.
If you haven't already, note that it's hard to make sure the editor doesn't load a cached version of the files. I recommend using the Developer Toolbar extension to disable the cache while working with this.
I can't give more detailed answers atm, but I'll try to get back to you later.

TPerkins’s picture

TPerkins commented

Wow... False alarm. It appears the whole 'no borders' thing is limited to my local development environment. Now that I have moved a fresh unedited copy of WYSIWYG and FCKeditor to our dev server, it has borders.

I'm relieved I'm not crazy.. Thanks for the help/reply anyhow.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Fixed

Gotta love those situations hehe. Then I'll be marking this as fixed if you don't mind.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.