with Safari 4.0.2
theme used: Garland (the standard theme when installing Drupal 6)
the fckeditor will only stretch something that looks like "5" rows (light blue colour) (probably because that is one of the settings) the rest of the field is not usable and not expandable. Looks like when you give a few enters, it gets the correct height anyway.

I wasn't able to set a width of the tables nor to get a handle to drag the tables to a specified size while I'm able to do this in Firefox.
Also with tables if you right click on a table then the side popup menu (the one around your cursor) can sometimes be at the top of the page or even higher making it not accessible at all. But with a bit of luck you can select the entire table and click the table button to edit the table properties, that works. Trouble is that if you want to modify a cell, row or column there is no such button displayed in the toolbar so you are really depending on that fly-out menu.
Are there buttons for cell, row and column properties?


Jorrit’s picture

Status: Active » Postponed (maintainer needs more info)

Does this only occur in Safari?

BassPlaya’s picture


I recently modified some of the code in the fckeditor.module file according to this link here: http://www.fckeditor.net/forums/viewtopic.php?f=6&t=14324 and in Safari this works but the field is still not "resizable" like a normal Drupal field without wysiwyg editor.

After a "flush all cache", delete browser caches and reload the browsers with the same user logged in I found that:
1. Firefox 3.5.2 still gives a tiny working window (very annoying)
2. Opera 9.20 just doesn't show the editor at all.
3. IE.. I'm not using IE but if you could have a look at IE and tell me that would be great! I'll probably soon find out when my customer is going to use it...
4. Safari (4.0.3 already) gives a much higher size of the window (about 30 to 40 rows)

Then I changed the amount of rows for that particular cck field to 20 rows.. and when the page is loaded (while default state enabled is set to true) It still gives the same results for Safari and Firefox (at this point I'm not checking Opera imho it's a worthless browser, too much trouble with that one. no offense) even "flushed all cache".

Then I tried to change the window of fckeditor in the fckeditor.module (as mentioned in that link ^^) to 600px, flushed all cache and this resulted in:

1. Safari takes the 600px but the table issue persists.. the lower you go (table with e.g. 30 rows) the higher the flyout menu pops up. Still no handles appear for resizing tables. However images are selectable (Ctrl+click to select the image and then select the image button from the toolbar). Table properties can be set by Ctrl+click.
2. Firefox has some minor issues when Ctrl+click. The popup menu appears in the correct place but it's difficult to let it disappear again.. weird. several normal clicks anywhere in the fckeditor field are needed.

Still I have 3 question:
1. are there any buttons to integrate with the editor in order to update/modify a cell, row, column or table as a whole for Safari? Or can the issue of selecting a table be resolved?
2. is there a way to resize the fckeditor field like a normal drupal field?
3. how does IE respond to fckeditor? Can anyone share their experience?

I hope my information could help out.

Cheers !

thebaron88’s picture

I'm pretty sure the first issue you had with half of the editor only showing was related to this - http://cksource.com/forums/viewtopic.php?f=6&t=13222
It's Webkit failing to resize the editor correctly.
Had to fix the issue for work, ended up with the following dirty fix,

In the file
the function
function FCKeditor_OnComplete(editorInstance) {
Insert the following 2 lines at the top of this function

var theBigFrameName = '#' + editorInstance.Name + '___Frame';
$(theBigFrameName).height($(theBigFrameName).height() + 10);

Works in chrome and safari on win, waiting on results from mac safari.
You could in theory then set the height back to the original, but we like the way it appears to consume the resize bar.

RikiB’s picture

#3 seems to have worked for me with Chrome

RikiB’s picture

Thanks btw.

Jorrit’s picture

Does version 2.0-beta2 work in safari out of the box or does it also need an adjustment?

Jorrit’s picture

Version: 6.x-1.3 » 6.x-2.x-dev
Status: Postponed (maintainer needs more info) » Fixed

I've just uploaded the fix of comment #3 for FCkeditor.module version 2.x-dev. Download that version tomorrow to see if it helped.

Status: Fixed » Closed (fixed)

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

Jorrit’s picture

I've undone the fix because the original problem was fixed in FCKeditor 2.6.5.