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


Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>

The "frame" parameter is no longer evaluated in the showpic eID as
it allowed uncontrolled resource consumption. This parameter was
actually never used by ContentObjectRenderer and existed since
the initial commit and is therefore put behind a feature flag.

Resolves: #103306
Releases: main, 13.1, 12.4, 11.5
Change-Id: I87019e58c078c8ccafc0b7ce42fe28b49dc068e4
Security-Bulletin: TYPO3-CORE-SA-2024-010
Security-References: CVE-2024-34358
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84259


Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>

Resolves: #103303
Releases: main, 13.1, 12.4, 11.5
Change-Id: I2842cefd5dfc0aff920e61b5fd16f029db8ada4c
Security-Bulletin: TYPO3-CORE-SA-2024-009
Security-References: CVE-2024-34357
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84258


Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>

Encode non prepared output of BackendUtility::getRecordTitle.
The string returned by getRecordTitle is only HTML encoded if
the third parameter (`$prep`) is set to true, ensure that
non-prepared usages are encoded on render.

Resolves: #103782
Releases: main, 13.1, 12.4, 11.5
Change-Id: I96b9530d118a21163d6679ebf7120aa40c7ac7b6
Security-Bulletin: TYPO3-CORE-SA-2024-008
Security-References: CVE-2024-34356
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84257


Tested-by: Oliver Hader <oliver.hader@typo3.org>
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>

The last used action is now properly resolved
again in the backend user module. Due to the
fact that accessing the module, extbase always
uses `index` as the selected action, the stored
user state was never resolved.

This is now fixed by using the index action
as forward action, forwarding to either the
stored default action or falling back the
new "listAction" which now acts as the main
entry point.

Resolves: #103692
Releases: main, 12.4
Change-Id: I764d130dc1a53a8fed25dadfaecaab5dd4eb58de
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84252


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

With #94499 creating redirects on page slug changes has been
enhanced to determine the source based on real url building,
respecting available site configuration route enhancer options,
for example PageTypeSuffix for page-type zero (`0`) in addition
to plain slug replacement generation.

The plain slug replacement does not take disabled state (`hidden`)
or scheduled state `starttime/endtime` into account, the advanced
url building using the PageRouter respected the context - which
discards hidden pages or pages outside the scheduled range.

To solve this issue, the `VisibilityAspect` in the context can be
changed to allow hidden and scheduled records which also revealed
a inconsistency between the option comment and the behaviour, and
the fact that this option has been missed. This has been addressed
with #103831 to enable this solution to work properly.

This change introduces a new internal method `getAdjustedContext()`
to `\TYPO3\CMS\Redirects\EventListener\AddPageTypeZeroSource` to
ensure a context to build uris for hidden pages and/or pages which
are scheduled and outside the constraint. The modified context is
used in `createPageTypeZeroSource()` instead of the current index.

Functional tests are added to cover this behaviour.

Resolves: #103436
Resolves: #103798
Related: #103831
Related: #94499
Releases: main, 12.4
Change-Id: I05cf793eacb7fb2f39c1ceeb72fcbd0bd3b16719
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84207


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

Attributes passed via TypoScript like:

```
page {
    includeJSLibs {
      someIncludeFile = EXT:sitepackage/...
      someIncludeFile.forceOnTop = 1
    }
```

were wrongly passed on to the `<script>` tag, resulting in:

```
<script src="/_assets/…" forceontop="1"></script>
```

This patch streamlines removing the specific `<script>` and `<link>`
tag attributes with a central function to prevent further copy+paste
differences, and better makes visible which TypoScript attributes
are removable for which type. Tests are added to ensure this works,
and can act as a regression check.

All of the keys that are unset from `additionalAttribute`s are handled
through their `addCssFile/addCssLibrary/addJsFile/addJsFooterLibrary()`
methods, and thus would not be emitted again.

Please note, this patch deals with one part of the issue. The other
portion about whether "data." is a good TypoScript subkey or not
is beyond scope, and was already fixed in documentation.

Resolves: #100954
Releases: 12.4
Change-Id: Icd0f7e958387c985b7373623a0fba3656120a57a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84206


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

Ensure env variable from port is cast to integer
when setting up TYPO3 with Environment variable
TYPO3_INSTALL_DB_PORT.

Resolves: #103826
Releases: main, 12.4
Change-Id: Ibd982690d3eec0527f452cd7353bdc0bf1a572c4
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84204


Tested-by: Benni Mack <benni@typo3.org>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Benni Mack <benni@typo3.org>

With #94499 creating redirects on page slug changes has been
enhanced to determine the source based on real url building
respecting available site configuration route enhancer options,
for example PageTypeSuffix for page-type zero (`0`) in addition
to plain slug replacement generation.

This included a check to drop the `PlainSlugReplacementSource`
if they match - which should be the case as long as no suffix
are defined for `page-type 0`.

Sadly, a default pagetype suffix is configured as slash similar to:

  routeEnhancers:
    PageTypeSuffix:
      type: PageType
      default: '/'
      map:
        '/': 0,
        '.json': 123

the generated slugs differs by the tailing slash - and thus creating
two similar redirects instead of one, which is expected.

This change modifies the duplicate detection in the corresponding
`\TYPO3\CMS\Redirects\EventListener\AddPageTypeZeroSource` method
`sourceEqualsPageTypeZeroSource()` to ignore tailing slashes for
the comparision. A functional test is added to ensure this behaviour.

Resolves: #103806
Related: #94499
Releases: main, 12.4
Change-Id: I0c07aeb8c13643cfed74de69e52a3a6fceb196cf
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84205


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

Since #102793 the PageRepository respects `includeScheduledRecords`
from the context `VisibilityAspect` setting in the `PageRepository`
and added a runtime cache  handling in the `init()` call. However,
the cache identifier does not respect the same visibilty options
for the cache identifier like it is used for preparing the property
`where_hid_del` - and thus leads to invalid and unexpected record
retrievement, depending on context switches in a request.

This change extends the cache identifier to respect the scheduled
record setting and removes the invalid page table except comment.

Resolves: #103831
Related: #102793
Releases: main, 12.4
Change-Id: I2e7f038a04d957751bba1181c3d5324c6e0674b5
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84236


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

It might be that pages are still available which are outdated regarding
its language. This can be when a site language has been removed from the
configuration.

Therefore those pages should be skipped when checking the integrity.

Resolves: #103801
Releases: main, 12.4
Change-Id: Ic5ca071ff8d2b5956365a432fa0f99da5772595f
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84203


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

When a content element (CE) gets edited or the visibility is toggled,
the page module is reloaded with an anchor in the URL to scroll to the
content element that was updated.

After #103381 it was not possible anymore to click the "+ Content"
button above such CE. The reason is that a pseudo element
`:target:before` is generated with a specific height and margin to
overcome the height of the floating module docheader, overlaying the
CE action button.
In the patch mentioned before, `overflow: hidden` was removed to make
the `box-shadow` of the CE visible, finally causing this bug.

To solve this issue the pseudo element add it #97036 is replaced by the
CSS option scroll-padding-top. It incorperates the maximum docheader
size plus a slight margin that is slightly lower than the grid margin –
but not equal to – to move shadows of adjacent elements out of sight.

Resolves: #103672
Related: #103381
Related: #97036
Releases: main, 12.4
Change-Id: I8d5c9eadd45e5507e39b1fb728de65d31c1d6689
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84234


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

This commit updates `phpstan/phpstan` to 1.11.0 and its related friends
to their latest respective version.

Executed command

    composer require --dev \
        phpstan/phpdoc-parser:^1.29.0 \
        phpstan/phpstan:^1.11.0 \
        phpstan/phpstan-phpunit:^1.4.0 \
        -W

Resolves: #103823
Releases: main, 13.1, 12.4
Change-Id: Idc057895d503089c03a8cb5358be4ea7e3575e93
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84223


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

New core-testing-* images has been build and published in
the TYPO3 testing-infrastructure repository and pulled to
the core ci gitlab runner instances. [1][2][3]

This change modifies `Build/Scripts/runTests.sh` to set
new image version to ensure the usage for all changes
based on this change.

For information what changed in the image see the patches
in the testing-infrastrucure repository linked below - at
least for the phpXY images.

* core-testing-php82: No change required, patchlevel image
  version change only and pulled on gitlab runner already.
* core-testing-php83: No change required, patchlevel image
  version change only and pulled on gitlab runner already.
* core-testing-apache24: Minor version release thus raising
  version required.
* core-testing-nodejs22: Minor version release thus raising
  version required.
* core-testing-nodejs22-chrome: Minor version release thus
  raising version required.

[1] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/df1e05ed52e724e0934e552c214395930022413b
[2] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/f754d7fbd2c3cbed98296c8a772869362487d073
[3] https://git.typo3.org/typo3/CI/testing-infrastructure/-/commit/4f93c5e93eb4e00fc936c13280918e60e62be567

Resolves: #103821
Releases: main, 12.4
Change-Id: I085cc0ce80682dfd009e5648f236974a380b8176
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84202


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

To circumvent race conditions where the cache is removed between
`has()` and `require()` invocations, the return value of the
cache result needs to be verified, as `false` is returned if
the cache entry is not available.

Resolves: #103720
Releases: main, 12.4
Change-Id: Iefede04108d3adf9bd6c77cb0600cdc994f6d0fa
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84216


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

When addressing flexform fields in TSconfig, the dots of the field names
have to be escaped with a backslash.

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


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

An error was made in [1] where a wrong link anchor name
(parseFunc) was used after refactoring the link format,
which leads to a warning in the documentation rendering
process.

[1] https://review.typo3.org/c/Packages/TYPO3.CMS/+/84193

Resolves: #103819
Releases: main, 12.4
Change-Id: I9b0c8f1852e32174b2ce5b59dc45607fd403a06c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84212


Tested-by: core-ci <typo3@b13.com>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>
(cherry picked from commit 9aee8dc8)
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84201

In advanced query the operator "is in list" makes value
be an array. Then switch the field to a non-array field
type, and you get the following TypeError:

```
  htmlspecialchars(): Argument #1 ($string) must be of type
  string, array given.
```

This resets the array value to an empty string.

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


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

The add widget modal has a cancel button on the bottom
of the modal now to match the other modal windows in
the backend.

Resolves: #103787
Releases: main, 12.4
Change-Id: I0c2c970b1148dfddadff1c3722d04dfcc939a69d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84197


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

Hook implementation are configured with the well known

    $GLOBAL['TYPO3_CONF_VARS']['SC_OPTIONS'][...][] = '';

syntax since ages. Directly defining an anonymous callback function
is undocumented and rarely used, but technical valid and supported
by the `GeneralUtility::callUserFunction()` method.

Due to the refactoring of the `ext:lowlevel` Configuration module
for the revamped TypoScript parser with TYPO3 v12 the code in the
`ConfigurationController` has been modified to do an array cast,
which triggers the execution of the function - which can lead to
some deep recursions and thus exceeding server resource limits.

Direct callback function should not be executed within the backend
Configuration module, which literally is a invalid execution of them.

Following code in a extension `ext_localconf.php` file will lead to
the resource limit issue:

    $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']
        ['tslib/index_ts.php']['preprocessRequest'][]
            = function($parameters, $parent) {};

This change modifies the `ConfigurationController->renderTree()` to
check if a value is a callable and display the information, and in
case of an anonymous function (`Closure::__invoke`) add additional
static information:

   Closure::__invoke (anonymous callback function: function() {})

Note: That does not make it obvious where the function is defined,
but it avoids calling these callback methods.

Resolves: #103813
Related: #99899
Releases: main, 12.4
Change-Id: I839d1668cf306100cf32af09ec9e24ad0120c43b
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84196


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

Resolves: #103812
Releases: main, 12.4
Change-Id: I467149ad6e93900cf917d3455b24dc01c97330f1
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84195


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

"Resources/Public" may occur also within an
asset path. Path detection code must therefore
only check for its first occurrence.

Resolves: #101701
Releases: main, 12.4
Change-Id: I8e0b62f5164593e472113ea8d294593e93abfe6c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84194


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

The ViewHelper documentation for f:translate mentioned
sprintf() from PHP, but did not link to it.

This patch adds a link and also optimizes markup, plus a few more
sprintf() examples with ordered parameters and number formatting.

See forge issue for screenshots how this looks before and
after the change.

Resolves: #103808
Releases: main, 12.4
Change-Id: I237d4b668291ad68bf083e35c0bdf6510158b38b
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84193


Tested-by: core-ci <typo3@b13.com>
Tested-by: Lina Wolf <112@linawolf.de>
Reviewed-by: Lina Wolf <112@linawolf.de>

Resolves: #103807
Releases: main, 12.4
Change-Id: Ifc551dcd66bc88da8c57e7213ee80d960f365509
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84192


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

The folder containing the charset conversion table files
should have the unicode license.txt file.

The license file is from https://unicode.org/license.txt

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


Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: core-ci <typo3@b13.com>

One part of the classname in a `throws` doc comment in
`MvcPropertyMappingConfigurationService` is wrong. Instead of
`EXTBASE` it should be `Extbase`.

Resolves: #103792
Releases: main, 12.4
Change-Id: I6be6e53640d82d39ff9f2ce99015877e693b8428
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84118


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Benni Mack <benni@typo3.org>

Executed commands:

    composer require --dev sokil/php-isocodes-db-i18n:^4.0.22
    Build/Scripts/updateIsoDatabase.php

Resolves: #103791
Releases: main, 12.4
Change-Id: I624ce17a6abaa2cb5c0479744db43bdf17cd069a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84145


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

The module `@typo3/backend/element/table-wizard-element` is tightly
coupled to FormEngine's `TextTableElement`, therefore said module is
moved to the FormEngine namespace. Additionally, the element gets
renamed to `typo3-formengine-table-wizard`.

Resolves: #103725
Releases: main, 12.4
Change-Id: I1c020a4ec6045007ab4c1f42289fe0a9c842f794
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84117


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

Commands:
composer req 'enshrined/svg-sanitize:^0.18.0'
composer req 'enshrined/svg-sanitize:^0.18.0' \
  -d typo3/sysext/core --no-update

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


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

With this change, the following changes have been applied to the
toolbar of the CKEditor "full" configuration preset:

* Remove superfluous `clipboard` toolbar item, since CKEditor 5 does
  not provide a UI for the clipboard plugin.

* Rename wrong `find` toolbar item to `findAndReplace`.

* Added `TableProperties` and `TableCellProperties` toolbar items.

* Move the `findAndReplace` toolbar item before the `link` toolbar
  item, because we also have this order in the `default` preset.

* Move the `selectAll` toolbar item to a dedicated group

Resolves: #103745
Releases: main, 12.4
Change-Id: I021b8c2f990c8e302bf169c3e368bf04928dd200
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84139


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

Allow the valid return type false which is returned by the function
exec on failure.

Resolves: #103778
Releases: main, 12.4
Change-Id: I8f0391efb6f890ebc0095ddb8a1f93ee9c36e18c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84116


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

Newer rollup major versions feature optimizations in build output.

The rollup source files are now natively parsed as ESM modules by
NodeJS. Earlier rollup versions implicitly transpiled ESM to CJS and
allowed a mixture of ESM and CJS imports (both `import` statements and
`require()` calls) in one module.

With the switch to ESM-only modules we now make use of `createRequire`
utility method when node-require resolution is needed for CJS path
lookups. Since our main project (Build/) is still in CJS mode by default
(for grunt), we apply a sub-project module type overwrite for the
Build/rollup/ folder via Build/rollup/package.json to ensure rollup
configuration runs in native ESM mode.

See https://nodejs.org/docs/latest-v18.x/api/packages.html
> Node.js will treat the following as ES modules when passed to node as
> the initial input, or when referenced by import statements or import()
> expressions:
> […]
> * Files with a .js extension when the nearest parent package.json ...

The node version used for building TYPO3 assets is raised to 22.0.
See https://nodejs.org/en/blog/announcements/v22-release-announce for
further details.

Resolves: #103780
Releases: main, 12.4
Change-Id: Ibc5b8c88ca5baedb7ae500adb5ef26a33617df4d
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84115


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

An error was previously shown and is now removed
if no backend type is selected.

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


Tested-by: core-ci <typo3@b13.com>
Tested-by: Benni Mack <benni@typo3.org>
Reviewed-by: Benni Mack <benni@typo3.org>

This patch addresses two key accessibility issues in the recycler
module: it adds a caption element to the table for better context
and provides labels for dropdown icons used in multi-selection,
ensuring screen reader compatibility.

Resolves: #103764
Releases: main, 12.4
Change-Id: Ia8b839cbc438396c8438969087d225c37a479bcf
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84107


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

The clear-input button now has a proper title and additionally an
aria-label to guide visually impaired users.

The button isn't read out by screenreaders when navigating the site
linearly (due to tabindex="-1") but when hold-pressing the button with
the mouse pointer, a screenreader will search for a human readable
label. We therefore add an aria-label attribute. The title attribute is
added for sighted users but will be ignored by screenreaders since it's
value equals the value of the aria-label attribute.

Resolves: #103417
Releases: main, 12.4
Change-Id: I4cbbe5200476a7d84ef1d675911ddd51f5899e87
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84106


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

The new factory method `HashValue::hash('test')` creates the
hash from the raw payload `'test'`. This is a simpler shortcut
for using `HashValue::create(hash('sha256', 'test', true))`.

Resolves: #103772
Releases: main, 12.4
Change-Id: Id201e166eeabc856b8d8dc498cc73cde8d5eb801
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84114


Tested-by: Georg Ringer <georg.ringer@gmail.com>
Tested-by: core-ci <typo3@b13.com>
Reviewed-by: Georg Ringer <georg.ringer@gmail.com>

This patch adjusts the flash message and notifications elements by
removing the h4 tag to prevent incorrect header flow throughout the
content structure, allowing for better flexibility based on different
use cases.

Resolves: #103762
Releases: main, 12.4
Change-Id: Ide330150145d5c4965410fbf61973ef682bb96b0
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84093


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

This patch adjusts the infobox/callout element by removing the
h4 tag to prevent incorrect ordering in the content structure,
allowing for better flexibility based on different use cases.

Resolves: #103761
Releases: main, 12.4
Change-Id: I2556ea0df0e55ffcdf752c9c0574b843ffea44ff
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84094


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

This patch enhances the accessibility of the link validator
module by ensuring proper relationships between table headers
and content cells.

Resolves: #103763
Releases: main, 12.4
Change-Id: Icef43369761f88705b491f3661252cc9a4b7ac0a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84092


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