Bug #24744
closed
Resizable textares not working in Chrome 9
Added by Andreas Becker (Andi) over 13 years ago.
Updated over 13 years ago.
Description
Typoscript Editor allows only to enter one character and than blocks until you click again with the mouse twice in the Editor where you want to edit, enter or delete the next letter.
We are using Chrome 9.0.597.67 beta on Ubuntu 10.10, TYPO3 4.5.0rc1, Framework for TemplaVoila, Debian 5 Server.
(issue imported from #M17235)
Can't reproduce, works for me with Chrome 9 on MacOS
Ah, indeed! I just encountered this issue. I thought you're talking of t3editor.
It's the resizable textarea TypoScript config in the page properties. You can type exactly one character, then nothing happens anymore.
Works in FF, breaks in Chrome9
Andreas, do you have some minutes to figure out, in what revision this problem was introduced? Or is it a general incompatibility with chrome 9 and also happens in TYPO3 4.4?
Okay, the resizable textareas don't work in Chrome 9.
In Chrome 8 they worked, also in TYPO3 4.4.
As Chrome 9 is still beta, I would not treat this as a blocker for 4.5 final, however it should be fixed soon.
Chrome 9 users can disable the resizable text areas for first aid..
Hi Steffen, I am going here actually:
WEB - Template - Choose a Page - Info modify - Edit the whole template record - Go to Constant or Setup - or description (while in description you can write AND afterwards delete one letter, delete direct afterwards is not possible in Constants and Setup)
in beta2 it is still working, so it came in beta3
Sounds hilarious, but this bug is caused by adding the CSS file admin_panel.css in #23644 (rev 9924).
Although none of the definitions matches any of the TCEforms elements (I think), it has this weird side-effect of making the textareas unusable.
This is my comment to #23644:
It really sounds hilarious, but this patch makes the resizable textareas in the backend unusable (*) in Chrome 9 (works in Chrome 8).
To be more specific: Adding the file admin_panel.css
I don't know how and why.. yes.. but it is how it is.
All definitions look well prefixed with #TSFE_ADMIN_PANEL_FORM, CSS validator and my two validator eyes also couldn't find any obvious issue.
So one question, which could remedy this problem: Has this file to be loaded in the backend? I don't think so, as it's loaded in lass.tslib_adminpanel.php. However, placing it in EXT:t3skin/stylesheets/(visual|structure)/ automatically causes it to be loaded in backend.
Could this file just be moved to t3skin/stylesheets/adminpanel/ or similar? This should fix the issue.
Fix is in #24802 and is pending on the core list. Any votes would be appreciated! Thanks!
Also available in: Atom
PDF