Bug #104152
closedcolorpicker preview not working in firefox
0%
Description
The preview color for the ColorPicker is not working.
It only shows after selecting a new color.
Files
Updated by Garvin Hicking 5 months ago
- Status changed from New to Needs Feedback
- Tags set to colorpicker
Hi!
Could you please provide some more details and steps to reproduce, also what kind of TCA configuration are you using?
Thanks!
Updated by Katharina Strasser 5 months ago · Edited
Garvin Hicking wrote in #note-1:
Hi!
Could you please provide some more details and steps to reproduce, also what kind of TCA configuration are you using?
Thanks!
Hi,
I tested this with 2 variants on a simple Type in list module:
'color' => array(
'exclude' => 0,
'label' => 'color',
'config' => array(
'type' => 'input',
'size' => 10,
'renderType' => 'colorpicker',
),
),
and
'color' => array(
'exclude' => 0,
'label' => 'color',
'config' => array(
'type' => 'color',
'size' => 10,
),
),
both show the same result.
Currently I'm using typo3 12.4.16
Updated by Garvin Hicking 5 months ago
Do you know the Extension "EXT:styleguide"? This one comes with a large number of TCA presets. In this case I verified this behaviour using the TCA element Form engine elements - input, text, checkbox, radio, none, passthrough, user
and there in the tab color
is the input element color_1
for example, see screenshot.
If I pick a color from there, it gets shown. Saving the element, and the color still is shown. If I close the edit view and re-open, and go to the tab again the color is also still shown properly.
This element is configured as:
'color_1' => [ 'label' => 'color_1', 'description' => 'type=color', 'config' => [ 'type' => 'color', 'size' => 10, ], ],
so the same like in your case. I tried this with both TYPO3 12.4.16 plus 13.2 (dev).
Do you maybe have an extension enabled that might interfer? Can you reproduce this on a simple, fresh TYPO3 installation (ideally using EXT:styleguide)?
Thanks a lot for your feeddback.
Updated by Katharina Strasser 5 months ago
Theres still no success with.
these are the only active packages
<?php
# PackageStates.php
# This file is maintained by TYPO3's package management. Although you can edit it
# manually, you should rather use the extension manager for maintaining packages.
# This file will be regenerated automatically if it doesn't exist. Deleting this file
# should, however, never become necessary if you use the package commands.
return [
'packages' => [
'core' => [
'packagePath' => 'typo3/sysext/core/',
],
'extbase' => [
'packagePath' => 'typo3/sysext/extbase/',
],
'fluid' => [
'packagePath' => 'typo3/sysext/fluid/',
],
'install' => [
'packagePath' => 'typo3/sysext/install/',
],
'backend' => [
'packagePath' => 'typo3/sysext/backend/',
],
'extensionmanager' => [
'packagePath' => 'typo3/sysext/extensionmanager/',
],
'filelist' => [
'packagePath' => 'typo3/sysext/filelist/',
],
'frontend' => [
'packagePath' => 'typo3/sysext/frontend/',
],
'styleguide' => [
'packagePath' => 'typo3conf/ext/styleguide/',
],
],
'version' => 5,
];
Its a non-composer installation running on php 8.2.19 (apache)
Then I tested the situtaion in another Browser, and the Colors are displayed.
Firefox does not display on inital colors while chrome does.
Updated by Garvin Hicking 5 months ago · Edited
That's a good clue. Which firefox do you use? I just tried the latest and funnily enough, it doesn't even show a screenshot like yours. There's no color indicator at all there, see my screenshot
(Wait, my bad - I checked this with v13, this seems to have changed there)
Updated by Katharina Strasser 5 months ago · Edited
its the version 127.0.1 on windows11
edit: same result on win 10
Updated by Garvin Hicking 5 months ago
- Subject changed from colorpicker preview not working to colorpicker preview not working in firefox
- Status changed from Needs Feedback to Closed
- Tags changed from colorpicker to colorpicker browser-issue
Ah!
I'm sorry. I just saw this one: https://github.com/TYPO3/typo3/commit/f6c4369ad86287a9bcaad14cca665e6dc2594ce4
We changed the colorpicker in TYPO3v13, so there'll probably be no change for this in v12 anymore adressing this browser issue, I'm afraid.
I will close this issue for now, if you feel this is a mistake or have additional feedback, please get in touch. You can also create a follow-up issue.