All in-tree .js files have been migrated to TypeScript, so it's
time to add a CI check to ensure no stray build files (see #101786)
or non-updated JavaScript files (e.g. #101784, #101785, #101787)
are present in the git tree.

Resolves: #101783
Related: #101784
Related: #101785
Related: #101786
Related: #101787
Releases: main, 12.4
Change-Id: I02aeaaeaae7fa0df634f39cb151f4316240936ab
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80869


Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Anja Leichsenring <aleichsenring@ab-softlab.de>

Resolves: #101856
Releases: main, 12.4
Change-Id: I41d3c07b44b544cd88e56e137dc0fb20ca38cb18
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80849


Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>

The TypeScript part of the FormEngine got the form element in a weird
way all over again. To make the code a little bit cleaner, the form
element is now accessed using a `FormEngine` getter property
in order to ensure types are properly infered.

Resolves: #101836
Releases: main, 12.4
Change-Id: I737287fc9a0b8fd94cc3bf915e7f1d2511c720ac
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80880


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

We are removing the obsolete .collapseIcon
wrapper and replace the icons directly.

Resolves: #101854
Releases: main, 12.4
Change-Id: I7c640eba173edc167910312087c46d6614d7f5c1
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80846


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Kott <benjamin.kott@outlook.com>
Reviewed-by: Benjamin Kott <benjamin.kott@outlook.com>

We also ensure that TYPO3.lang checks are correct
when the modal is used in a context where TYPO3.lang
is not defined.

Resolves: #101844
Releases: main, 12.4, 11.5
Change-Id: I1e6e90ed86e72f483929429b8e2c833179b60f87
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80867


Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

The parser originates from the original codemirror javascript-mode
and therefore contains a lot of legacy and unneeded code.
Code that is obviously unneded for TypoScript (like
backticks (called "quasi") or function expressions are removed
to reduce the amount of code that needs to be type-declared.

Resolves: #101803
Related: #101783
Releases: main, 12.4
Change-Id: If048e8c914cad3953463e9af712908f0e84c5f8f
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80852


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

The image cropper component uses buttons to let a backend user toggle
the currently active aspect ratio setting, indicated via an `active`
class and a checkmark icon. With the removal of Font Awesome in #97877,
some CSS was removed that was responsible for toggling the visibility of
the checkmark icons.

This patch adds the missing CSS again, including necessary adaptions to
Core's Icon API.

Resolves: #101788
Related: #97877
Releases: main, 12.4
Change-Id: I1daf428cafba3bc5f1e707c2763bf3f5dd6ba293
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80842


Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>

Resolves: #101845
Releases: main, 12.4
Change-Id: I1ba482f9f482a9579a6d0295cde161de83d5bebf
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80864


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>

With #101782 eslint project configuration was overwritten
to use a custom path.
eslint read the relative project configuration based
on the current execution folder instead of relative
to the eslintrc file.
This worked as long as eslint was executed from the
Build/ folder (execution folder == eslintrc folder).

As some tools execute eslint from the git root directory,
the configuration is now adapted to always resolve the
tsconfig file name as an absolute path based on the
configurations directory name.

Also overrideConfigFile is removed from Gruntfile.js
as .eslintrc.[json|js] is read by default and no
override is needed.

Resolves: #101846
Related: #101782
Releases: main, 12.4
Change-Id: I58a6322a74d388efb0da28d1d8e7375f491c7aea
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80841


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

Now that our build chain targets ESM modules, we can
use our TypeScript toolchain to also build utility
entry point scripts, allowing to make use of TypeScript
checking and centralize asset management.

Resolves: #101790
Related: #101783
Releases: main, 12.4
Change-Id: I2b4e89114022a611a0e061d16d012e4b389dc750
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80830


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

Resolves: #101795
Related: #101783
Releases: main, 12.4
Change-Id: Id881225a77fcbb0fa6dbd9a7e75caba4fbe05ab1
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80821


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

FormEngine sends some information as payload with the suggest
wizard ajax request to the `SuggestWizardController` as context.
The controller loads the record based on the tableName and
the uid to determine the recordType to read the correct TCA field
configuration, respecting special overrides like `columnsOverrides`.

If a new record is created, there is no record uid available and
passed to the controller. Therefore, the recordType is not properly
determined. That leads to wrong record suggestions, if for example
the `allowed` record table is overriden for specific recordTypes.

This change adds the recordTypeValue as additional html data
attribute to the suggest search field, reads and sends it along
with the context payload in the ajax request to the suggest
wizard controller, which now uses the passed value while keeping
the record retrievement as fallback for now.

Suggest records are now directly searched correctly respecting
the full TCA configuration for the type, even for new records.

Additionally, uid is send as null instead of the string "NaN".

Used command(s):

> Build/Scripts/runTests.sh -s buildJavascript

Resolves: #101796
Releases: main, 12.4, 11.5
Change-Id: I3b814d37b7d4d3e9674ad6f2af882520c4f91413
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80773


Tested-by: Stefan B�rk <stefan@buerk.tech>
Reviewed-by: Stefan B�rk <stefan@buerk.tech>
Tested-by: core-ci <typo3@b13.com>

See: https://github.com/ckeditor/ckeditor5/issues/14200#issuecomment-1625171318

This allows similar behaviour as CKEditor 4 with applying styles to block components as DocumentList is preferred over List.

Resolves: #100348
Releases: main, 12.4

Change-Id: I155889e37ca1e63b27aed0d01dad2154da5bd37e
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80689


Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>

DataMapProcessor tries to access `$possibleChainedIds[0]` which
might not be defined, since that array is the result of a previous
`array_intersect` invokation, which keeps the array keys of the
original input array.

DataHandler tries to access `$this->copyMappingArray[$table][$uid]`,
which might not be defined in case the previous copy command could
not be executed (e.g. since the record was deleted already).

Resolves: #101748
Releases: main, 12.4, 11.5
Change-Id: Ibcbc412c7df62ce17dfa2c0f6fc120ccebb953d8
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80670


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Oliver Klee <typo3-coding@oliverklee.de>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>

@lezer/common – in contrast to other @lezer modules,
is placed in dist/index.js instead of dist/index.es.js.
Therefore we add a distinct copy rule.

The sortablejs npm package recently changed to provide both,
a UMD bundle and a native ESM module.
As we actually failed to update the UMD bundle (due to a
rename of the build output filename in sortablejs),
we switch to the new ESM variant right away.

muuri failed to update because dashboardToEs6
was missing in the npmcopy concurrent target.

Resolves: #101784
Resolves: #101785
Resolves: #101787
Related: #101783
Releases: main, 12.4
Change-Id: I2ccf69847876edb55f089a4a5142ac388699fb54
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80687


Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>

IDEs like PhpSstorm complain about the same thing,
so better we have that defined and checked via CI.

Commands executed:
  node_modules/.bin/eslint --fix Sources/TypeScript/

Resolves: #101780
Releases: main, 12.4
Change-Id: I01e0289b671dfd4348319bca90dddaec085fbfe4
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80747


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

This helps to prevent hard-to-discover build failures, that only
happen on clean installs (e.g. CI).
This is because TypeScript will by default scan the entire source
dictionary (Build/ in our case) for possible includes.
We previously excluded /Build/composer in #95046, but it is actually
much better to explicitly include the actually used source paths
to also exclude build output (Build/JavaScript/) from being
reinterpreted by subsequential eslint or tsc compile runs.

Note that we also refactor the types/ directory in order to
be a folder that conforms to the @types/* packages conventions,
by being actually usable in the compilerOptions.types property.

Note that our custom global type definitions (types/) were previously
implicitly loaded as globally available sourcepaths.
With the new `include` option we could add them back, but then we
wouldn't notice if we do not add proper index.d.ts files (like we
did until now). Therefore index.d.ts files are added in here.

Now, with TypeScript being "clean", we need a another small
adjustment in order for eslint to still being able to lint
our types/ folder. Therefore tsconfig.json is extended to
include the types directory. See [1] for more information on
why eslint needs that.

[1] https://typescript-eslint.io/linting/troubleshooting/#i-get-errors-telling-me-eslint-was-configured-to-run--however-that-tsconfig-does-not--none-of-those-tsconfigs-include-this-file

Resolves: #101782
Related: #95046
Releases: main, 12.4
Change-Id: I3ab8b874192d25470bbd5e71cc5d99e853259f89
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80746


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>

This allows to drop a npm patch that had been applied
to the TypeScript @types/jquery before, in order
to achieve the same effect.
With eslint we can additionally provide a good
hint for the developer, what to use instead.

For the v12 backport @types/jqueryui is removed
additionally, as it conflicts with the bootstrap
jquery definitions and was unused. This showed
a small adaption that needed to be changed in
upgrade-docs, which has already been fixed
in main and is reapplied in here.

Commands executed:
  npm remove patch-package
  npm install
  npm remove @types/jqueryui

Resolves: #101697
Releases: main, 12.4
Change-Id: I77e15a4b4c2a18f8b72ec2a5f41c7e54a7966c30
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80686


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

The Install Tool router attempts to build URLs manually by wild string
replacements and manipulation, which is rather error-prone. This patch
changes the approach to use the URL API instead.

Resolves: #101789
Releases: main, 12.4
Change-Id: I07ee73764b4fc5167f732d67faf2843fef0db199
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80745


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

…of a new form element, that has not yet been persisted.

Tabbing through an elemenet is considered an "input" by
the browser, which is why the "input" even is triggered.
The result is an empty input element (as before), but
an intent is made to delete the underlying property
from the form element object model.
When the object model is empty (remeber, it is a new element),
and an input field refers to a nested property
(e.g. properties.fluidAdditionalAttributes.placeholder)
removing an element (e.g. 'placeholder')
will fail when the parent has not yet been set
(e.g. properties.fluidAdditionalAttributes)

Resolves: #101750
Releases: main, 12.4, 11.5
Change-Id: I49a9ead343e671c3d0289bd6d969316b888d05eb
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80729


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Kott <benjamin.kott@outlook.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Benjamin Kott <benjamin.kott@outlook.com>

Previously, the `keyup` event was intercepted in "Extension
Configuration", which doesn't work with `clearable()`. This patch
changes the code to listen to `input` and `change` events instead.

Resolves: #101772
Releases: 12.4
Change-Id: I1e90ede6ab1693fd76dcb6aafb1dab0a616b5784
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80714


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

With #90002, all occurrences of the `list()` function have been migrated
to the short list syntax. Our php-cs-fixer configuration does however
not check the short list syntax usage, so we have one usage of `list()`
in our codebase again.

This change extends the php-cs-fixer configuration to ensure, that
only the short list syntax is used. The new ruleset has been applied
to the codebase and one usage of the `list()` function has been migrated.

Resolves: #101777
Related: #90002
Releases: main, 12.4
Signed-off-by: Torben Hansen <derhansen@gmail.com>
Change-Id: I30f5822e27a36515c2c77a19089a0754ff6fdcfd
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80684


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101738
Related: #82577
Releases: main, 12.4
Change-Id: Id857430ae81322cf9197ba6df422780695f59f50
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80728


Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101737
Related: #82577
Releases: main, 12.4
Change-Id: Ibc8ed8be6a8defc7dba4910e3f1df937809600aa
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80727


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

Resolves: #101736
Related: #82577
Releases: main, 12.4
Change-Id: If77dc697ac23b5f1fb3f36dd15fe36cfb369700d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80726


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101735
Related: #82577
Releases: main, 12.4
Change-Id: I5584528f69fddba7a5f7f4b3592ca4bf9e83938c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80725


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

Resolves: #101734
Related: #82577
Releases: main, 12.4
Change-Id: I0619297a3fbf3e2fd18b1aef1a0c82794a5ca714
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80724


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101733
Related: #82577
Releases: main, 12.4
Change-Id: I4d9f92287d9a2b69fa4421de2377f7bf9806147c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80723


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101717
Related: #82577
Releases: main, 12.4
Change-Id: I9e0a42954b387d34ded5ebd1bde533b9feb4e70e
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80722


Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101713
Related: #82577
Releases: main, 12.4
Change-Id: Ic7b41b79552a4c14d7395609e0ac3dda9c47b20f
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80721


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101712
Related: #82577
Releases: main, 12.4
Change-Id: Id77b6cd93cff41c26220ca0b10b948813c1242be
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80720


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

Resolves: #101702
Related: #82577
Releases: main, 12.4
Change-Id: I4ec165e645ee367d71404338e83ba6f40cb28494
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80719


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>

Resolves: #101634
Related: #82577
Releases: main, 12.4
Change-Id: Ia9ad4d39e925f671707ec62cd989bfca6dbf32ab
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80718


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

When resetting the tag filter in "View Upgrade Documentation", the
`hidden` class now gets removed, making previously filtered upgrade docs
visible again.

Resolves: #101771
Releases: main, 12.4
Change-Id: Ie8bc14cc20fed803ae9644308eeb7cf2daa15a09
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80715


Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Andreas Fernandez <a.fernandez@scripting-base.de>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de>

The ajax Icon API is currently not available during
first install, therefore neither getIcon nor the
icon web component may be used to render an icon.
The icon markup is therefore now pre-rendered
via fluid for both states and toggled via CSS.

Resolves: #101765
Related: #98089
Releases: main, 12.4
Change-Id: Ib72c06e41f083e4dc7392845058fc86aae95af9c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80712


Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

With CKEditor v38.0.0 a small "Powered by CKEditor" logo has been added
to the bottom right of the editor component. The logo is visible as soon
as the CKEditor component receives the focus. The current placement of
the logo does however overlay the border of the editor component and the
term "Powered by" does not suit well to the TYPO3 backend.

With this change, the CKEditor configuration has been extended, so it is
now possible to configure `config.ui.*` settings. The `Base.yaml` file
has been extended with CKEditor UI specific settings, which remove the
term "Powered by" from the logo and which optimize the logo placement,
so it appears in the bottom right corner of the editor component without
overlaying the border.

Resolves: #101759
Releases: main, 12.4
Signed-off-by: Torben Hansen <derhansen@gmail.com>
Change-Id: Ic35054a92c7101fac9381e1476c214ffad3e0465
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80678


Tested-by: Jasmina Lie�mann <minapokhalo+typo3@gmail.com>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Jasmina Lie�mann <minapokhalo+typo3@gmail.com>

The Filelist module got renamed to "media_management" from
"file_FilelistList" in TYPO3 v12. Hence, the module storage identifier
needs to be changed to "media" as well.

Resolves: #101685
Related: #100279
Releases: main, 12.4
Change-Id: Ic2e5b06426411f122551b0745fb43b18497b247c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80594


Tested-by: Nikita Hovratov <nikita.h@live.de>
Reviewed-by: Nikita Hovratov <nikita.h@live.de>
Tested-by: core-ci <typo3@b13.com>

Fix handling link attributes (such as target, title)
in link browser. The attributes were formerly not
always applied to the link currently being edited.

The problem appeared to be that the current selection
in the editor lost focus and when link attributes
were handled for this case, only the href attribute
was applied.

This is a follow-up patch for patch
https://review.typo3.org/c/Packages/TYPO3.CMS/+/80034
which did not fully resolve problems with setting the
link attributes.

Resolves: #101638
Related: #101360
Related: #101205
Releases: main, 12.4
Change-Id: Id5aeaae11341169b7a7bda15f62aeb2937486f88
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80576


Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Nedbal <andy@pixelde.su>
Reviewed-by: Andreas Nedbal <andy@pixelde.su>

The methods `createRenderRoot()` and `render()` are considered being
protected, but were public in some cases my mistake. This doesn't have
any functional impact, but is now fixed nonetheless.

Resolves: #101689
Releases: main, 12.4
Change-Id: I6bb88f90a8a44e0118dd8203433a54517b5dfa2f
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80561


Tested-by: Benjamin Franzke <ben@bnf.dev>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>

Google Chrome (and other browser vendors will probably follow)
deprecates the unload event with Chrome 117 [1] and encourages using
the Page Lifecycle API [2] instead. This patch replaces any usage of
the `unload` event with the `pagehide` event that is available for all
supported browsers [3].

[1] https://developer.chrome.com/en/blog/deprecating-unload/
[2] https://developer.chrome.com/blog/page-lifecycle-api/
[3] https://caniuse.com/mdn-api_window_pagehide_event

Resolves: #101662
Releases: main, 12.4, 11.5
Change-Id: I675b180e855d8fb1070a84f5ba865e9250b2c0aa
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80559


Tested-by: Benjamin Franzke <ben@bnf.dev>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benjamin Franzke <ben@bnf.dev>