Bug #102051
closed
Environment -> Image Processing instantly closes after opening on cold browser caches
Added by Stefan Bürk about 1 year ago.
Updated about 2 months ago.
Category:
Backend JavaScript
Description
If I reload the backend clearing the browser cache / avoiding that resouces
and JS are used from cache and click on "Enviorenment -> Image Processing"
the modal opens, and nearly instantly (~1 sec) closes - leaving a buttom html
markup displayed in the JS console of the browser. The second click opens the
modal normally - and every click after that.
Found in main, not tested yet in v12 or earlier.
One note - I start my chrome with:
/usr/bin/google-chrome-stable %U --force-dark-mode --force-prefers-reduced-motion
Edit
- Environment -> PHP Info same effect
- Environment -> Directory Status (no modal opened, only backdrop shadow) leaving backend broken
Files
- Description updated (diff)
- Description updated (diff)
- Status changed from New to Needs Feedback
There is a "logic.js" file mentioned in the screenshot that outputs "Found pop up - standard way".
We don't have a file with that name nor such message.
I suspect this is a browser extension.
Can you see what opens, when you click on "logic.js" and check if the same behavior happens in inkognito mode?
- Environment -> Directory Status (no modal opened, only backdrop shadow) leaving backend broken
Same problem with "Directory Status" for us with TYPO3 13.0.0 and current Chrome + Firefox, no error in console.
Additionally in Firefox modal of "Environment Status" is open but empty probably because of an js-error, in Chrome it works.
- Status changed from Needs Feedback to New
- Status changed from New to Needs Feedback
Is this still an issue in 13.3? I cannot reproduce this.
Andreas Kienast wrote in #note-6:
Is this still an issue in 13.3? I cannot reproduce this.
Since 13.1 we don't have any problems like described before. Perhaps fixed with #103048 / #101224?!
- Status changed from Needs Feedback to Rejected
I'm closing this one since the issue mentioned by "Wittkiel Gruppe" had another cause (web components in cross-frame contexts) and the original issue was triggered by a browser extension which we can't workaround.
Also available in: Atom
PDF