Project

General

Profile

Actions

Bug #21369

closed

JavaScript-Error with "useSortable => 1" with more than one inline element

Added by Lee Perry over 14 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2009-10-26
Due date:
% Done:

0%

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

Description

With more than one element, inserted in an inline area (IRRE), I've got the following JavaScript-Error when I have enabled the useSortable ("useSortable => 1"):

An invalid or illegal string was specified" code: "12
typo3/contrib/prototype/prototype.js Line 2844
results = $A(root.querySelectorAll(e)).map(Element.extend);\n

Because of this error the JavaScript is stopped and so the values of other fields will stay empty and I cannot sort the inline elements.

With only one inserted element or with the disabled useSortable option I've got no error.
In earlier TYPO3 versions like 4.2.10 I've got no error, as well.

I hope this is only a small JavaScript error which can be easily fixed ...

(issue imported from #M12352)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #21349: DOM object identifiers use invalid charactersClosedOliver Hader2009-10-23

Actions
Actions #1

Updated by Lee Perry over 14 years ago

Oh, I've realised now, that this seems to be a problem of modern browsers only, because this is a problem in Firefox 3.5.3, but not in Firefox 2.0.20 and a problem in IE8 mode but not in IE7 compatible mode and also a problem in Opera 10.0 ...

Actions #2

Updated by Oliver Hader over 14 years ago

Hi,
the problem can be found in CSS selectors modern browsers use (e.g. "#element.className") instead of using an elderly document.getByClassName(). You can try "0012327_v2.patch" of this issue #21349 which should solve these problems.

Actions #3

Updated by Lee Perry over 14 years ago

Hi,
sorry for the late response ...
the patch is working fine and the problems are solved.

thanx!

Actions #4

Updated by Oliver Hader over 14 years ago

This issue was solved by RFC #21349

Actions #5

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF