Project

General

Profile

Actions

Bug #17168

closed

Link popup don't have scrollbar with compressed script and patch for FF2.0.0.3 (see 0005266)

Added by Christophe Monard about 17 years ago. Updated almost 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2007-03-29
Due date:
% Done:

0%

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

Description

Enabling the compressed script in RTE cause the scrollbar to disapear in link creation window.

Don't have the time to see where in the compressed script it block, but I think it's that (can be reproduce on all my plateform).

Christophe MONARD (Métaphore Multimédia)

(issue imported from #M5321)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #17136: htmlarea doesn't load with new Firefox 2.0.0.3ClosedPatrick Broens2007-03-21

Actions
Actions #1

Updated by Oliver Hader about 17 years ago

I could not reproduce this on latest SVN revison of TYPO3_4-1 and Trunk.
What TYPO3 version and or RTEhtmlarea version are you using?

Actions #2

Updated by Christophe Monard about 17 years ago

Problem show on :
- Typo3 4.0.5
- rte html area 1.4.3 with latest FF 2.0.0.3 diff patch.

Actions #3

Updated by Patrick Broens about 17 years ago

I could not reproduce it myself, even with the given configuration

Do you get any javascript errors?

Actions #4

Updated by Oliver Hader about 17 years ago

You can upgrade your local extension to RTEhtmlare 1.4.4. I've uploaded the new version to TER today.

Actions #5

Updated by Christophe Monard about 17 years ago

No script error (firefox developper toolbar test) with RTE 1.4.3 compressed script : still no scroll bar.

Tested RTE 1.4.4 compressed script : no problem at all, scroll bar appear.

Don't really understand what's wrong.

I've keep my 1.4.3 version if needed in future.

Actions #6

Updated by Patrick Broens about 17 years ago

So we can assume this problem is resolved with version 1.4.4? Then we can put the status of this bug to 'resolved'.

Actions #7

Updated by Christophe Monard about 17 years ago

Yes it's resolved (tested on 3 install)

Actions #8

Updated by Patrick Broens about 17 years ago

Changing status to resolved. Works in version 1.4.4

Actions

Also available in: Atom PDF