Project

General

Profile

Actions

Bug #16692

closed

htmlArea RTE conflicts on using prototyped Array objects (e.g. Prototype JavaScript framework)

Added by Oliver Hader over 17 years ago. Updated about 17 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2006-11-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

TYPO3 Ver. 4.1-dev

In htmlarea.js there are some lines of code, that walk through an array like this:
for (var plugin in RTE["plugin"])

But some of these class variables (RTE['plugin'] is one of them) are defined as "Array", not as "Object". So, if the code from above walks through RTE['plugin'] it also processes prototyped variables, that are not really part of the JavaScript array and throws a JavaScript exception in the browser.

Solution: Change "new Array()" for usage on associative array to "new Object()".
See my experimental changeset at http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/changeset/5716

The Inline Relational Record Editing Project uses prototype.js to handle AJAX calls and to do some DOM-stuff. On using the htmlArea RTE together with Inline Relational Record Editing, the mentioned errors occur.

see http://wiki.typo3.org/index.php/Inline_Relational_Record_Editing
(issue imported from #M4469)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #16868: each is not definedClosedOliver Hader2007-01-20

Actions
Actions #1

Updated by Oliver Hader over 17 years ago

Fixed in SVN Trunk (rev. 1809)

Actions

Also available in: Atom PDF