#106170Attaching images to content elements via element browser is broken in Firefox
Description
It seems with Firefox (134.0.2) the changes in element-browser.js create an error, which does not happen with Chromium. It somehow seems related to CORS and the FF security model for accessing a frame?
See screenshot.
Reverting element-browser.js to the version of TYPO3 13.4.4 makes it work again.
Slack discussion thread: https://typo3.slack.com/archives/C025BQLFA/p1739386874937549
Reviews 3
Related issues 2
Files 2
History 813
-
Garvin Hicking changed Related to #97466 Related to #105172 <span data-processor="relativetime" data-value="2025-02-13T13:59:49+00:00" > 02/13/25, 13:59 </span>
-
Garvin Hicking changed description <span data-processor="relativetime" data-value="2025-02-13T14:00:11+00:00" > 02/13/25, 14:00 </span>
-
Garvin Hicking changed subject
Attaching images to Content elements is brokenAttaching images to content elements via element browser is broken in Firefox <span data-processor="relativetime" data-value="2025-02-13T14:02:31+00:00" > 02/13/25, 14:02 </span> -
Garvin Hicking commented <span data-processor="relativetime" data-value="2025-02-13T22:49:43+00:00" > 02/13/25, 22:49 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 88212 status
NewUnder Review <span data-processor="relativetime" data-value="2025-02-13T23:03:33+00:00" > 02/13/25, 23:03 </span> -
Gerrit Code Review pushed patch set 2 for main to change 88212 <span data-processor="relativetime" data-value="2025-02-14T10:46:42+00:00" > 02/14/25, 10:46 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 88212 <span data-processor="relativetime" data-value="2025-02-14T10:55:54+00:00" > 02/14/25, 10:55 </span>
-
Oliver Hader changed attached Screenshot 2025-02-14 at 12.02.04.png <span data-processor="relativetime" data-value="2025-02-14T11:04:08+00:00" > 02/14/25, 11:04 </span>
-
Oliver Hader commented <span data-processor="relativetime" data-value="2025-02-14T11:12:56+00:00" > 02/14/25, 11:12 </span>
Side-note:
I registered a free account of LastPast.com, installed the browser extension and was able to reproduce the original (faulty) behavior.
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 88245 <span data-processor="relativetime" data-value="2025-02-17T09:57:17+00:00" > 02/17/25, 09:57 </span>
-
Gerrit Code Review pushed patch set 1 for 12.4 to change 88246 <span data-processor="relativetime" data-value="2025-02-17T09:57:27+00:00" > 02/17/25, 09:57 </span>
-
Garvin Hicking commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-02-17T10:00:11+00:00" > 02/17/25, 10:00 </span>Applied in changeset commit:c238621247e51ded79eb89b5cda5e9b2d23d641d.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-08-12T14:36:33+00:00" > 08/12/25, 14:36 </span>
Update: The reason is LastPass. It seems to inject custom iframes, which the new JS code tries to access (because it thinks the iframes belongs to TYPO3).
A solution would be to check the iterated iframes if they are really accessible.