Opened 12 years ago

Closed 11 years ago

#269 closed Bug (wontfix)

Javascript error: FCKTools.GetElementWindow(A) has no properties

Reported by: Pontus Kindblad Owned by: Martin Kou
Priority: Normal Milestone: FCKeditor 2.6
Component: General Version: FCKeditor 2.4
Keywords: Cc:

Description

Javascript error: FCKTools.GetElementWindow(A) has no properties fckeditor/editor/js/fckeditorcode_gecko.js Line: 80

Are using the Toolbar "out" setting.. works if it is not "out". Using firefox 2.0.0.2
Example: http://agda.strangeways.se/demo/
click on admin and log in as: root/toor

Then click on the pen(edit) icon.

Change History (5)

comment:1 Changed 11 years ago by Frederico Caldeira Knabben

Keywords: Pending WorksForMe added; Javascript error: GetElementWindow removed

I can't see the error. Can you confirm it has been fixed?

comment:2 in reply to:  1 Changed 11 years ago by Pontus Kindblad

Replying to fredck:

I can't see the error. Can you confirm it has been fixed?

This was not actually fixed, but i got help with a workaround. When we used a toolbar:out, it happend if the connection was slow. So we inserted a 3 second delay before creating the fck object and that worked.

comment:3 Changed 11 years ago by Frederico Caldeira Knabben

Keywords: Pending WorksForMe removed
Milestone: FCKeditor 2.6

It is just a theory...

It seams that, probably in slower connections, not locally, the editor tries to create the toolbar in an element outside its frame (ToolbarLocation='Out:xToolbar', for example), but the element ("xToolbar") is not yet available in the DOM, as probably the page has not been entirely loaded.

Maybe placing the target element as the first one inside <body> also helps solving it, but the correct solution is implementing an event mechanism that fires the toolbar creation only then the target page has been completely loaded, so we are sure that the target element exists.

Actually, in your code Pontus, You are calling ReplaceTextarea right after rendering the textarea, and not in the window.onload event, which is the recommendation and which would certainly make you page work correctly..

comment:4 Changed 11 years ago by Martin Kou

Owner: set to Martin Kou
Status: newassigned

comment:5 Changed 11 years ago by Martin Kou

Resolution: wontfix
Status: assignedclosed

Wontfix because the bug does not occur as long as the web developer follows reasonable guidelines. Also the test site was down so it's difficult to determine what went wrong here.

Note: See TracTickets for help on using tickets.
© 2003 – 2017 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy