This project is mirrored from https://git.typo3.org/typo3/typo3.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
- 09 Jul, 2021 1 commit
-
-
The validation is already done in the FormEngineValidation on load. In the method loadDataAfter the tree nodes are not yet loaded for whatever reason and thus the validation always fails if having minitems set. Resolves: #94466 Releases: master Change-Id: I47b0c3bcbb64887239ba30b1a56fbc5681072120 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69731 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
-
- 14 May, 2021 1 commit
-
-
Executed command: yarn add "bootstrap@^5.0.1" Also, some minor coding issues were solved that popped up with the update. Resolves: #94138 Releases: master Change-Id: Ie80eff09efba43cfb9ae60862cb2167b0bc3f12f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69146 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Richard Haeser <richard@richardhaeser.com> Tested-by:
-
- 11 May, 2021 1 commit
-
-
Since the bootstrap v5 update, the inputLinkElement is styled with flex form instead of display table. This became a problem, because this broke the appearance of the explanation toggling. The initial idea to hide the complete clearable wrap didn't work properly as it is loaded dynamically and it's not ensured it exists when trying to hide it. To circumvent this problem, the styling is now done with some extra css. Additionally the wrong form-control class is removed from the clearable wrap and the styling is now also moved to own css. Resolves: #93941 Releases: master Change-Id: I0bb0d1cf26ed40dd3c87a58e08cc39e449b96c0d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69064 Tested-by:
core-ci <typo3@b13.com>
Tested-by: 
Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 23 Apr, 2021 1 commit
-
-
Benjamin Franzke authored
Lit is the umbrella term for the next major lit-html (v2) and lit-element (v3) versions. Therefore we will refer to these components as *Lit* in TYPO3 from now on as well. These two libraries also have been migrated into a single entry point module named `lit`. It is officially described as: > The main module exports the core pieces needed for component > development: LitElement, html, css, and the most lit-html v2 and lit-element v3 are mostly compatible to the previous major versions. Main changes are * Deprecation of the `lit-element` entry point in favor of the new `lit` module * @internalProperty changed to @state * shadow css declaration via static property instead of static getter method * The CSSResult type declaration is gone * Directive (currently unused in TYPO3) API has changed Related testing framework change is: https://github.com/TYPO3/testing-framework/pull/229 Commands used: rm -rf typo3/sysext/core/Resources/Public/JavaScript/Contrib/{@lit,lit-element,lit-html,lit}/ yarn add lit@^2.0.0-rc.1 lit-html@^2.0.0-rc.2 lit-element@^3.0.0-rc.1 yarn add --dev rollup@^2.32.0 @rollup/plugin-replace grunt build git add typo3/sysext/core/Resources/Public/JavaScript/Contrib/{@lit,lit-element,lit-html,lit}/ composer require --dev typo3/testing-framework:^6.8.1 composer require --dev typo3/testing-framework:^6.8.1 \ --no-update --working-dir=typo3/sysext/core Resolves: #93965 Releases: master Change-Id: I9b659d851e6ad9dc3cc649bd40aab886b86fb0f8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68104 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
core-ci <typo3@b13.com>
Tested-by: Benjamin Franzke <bfr@qbus.de> Reviewed-by:
-
- 13 Apr, 2021 1 commit
-
-
This patchs adds a new LitElement that invokes the update request of FormEngine if a field's value with such configuration changes. This replaces the current approach of huge onchange/onclick attributes rendered per affected field. A further patch will cleanup the necessity of TBE_EDITOR.fieldChanged(). Resolves: #93899 Releases: master Change-Id: I79aa5b6ab7cca9b555efaafcadabcc623567af64 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68756 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
- 07 Apr, 2021 1 commit
-
-
When regenerating a slug value via form engine in the backend user interface, changed states are not addressed anymore. Corresponding JavaScript `change` event has to be triggered for the element that is used to trigger changes for form engine validation. Resolves: #93874 Releases: master Change-Id: I7e78f36f4434009c122717eeb92bc463b9daa1a6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68722 Tested-by:
Xavier Perseguers <xavier@typo3.org> Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 19 Mar, 2021 1 commit
-
-
This change reduces the overhead of the d3 framework by using native CustomEvents on the actual Lit element of the SVG instead of d3-dispatch logic: * typo3:svg-tree:nodes-prepared (enrich node data) * typo3:svg-tree:expand-toggle (expand/collapse) * typo3:svg-tree:node-context (clickmenu) * typo3:svg-tree:node-selected (on-click) As shown in the patch, the actual logic of interacting with the outside framework (Persistent, ContextMenu, window.) is moved to the actual Lit components, making the SVG tree slimmer and easier to maintain. Resolves: #93782 Releases: master Change-Id: I6f5227579eb16ec218bbe67de2aecbcaaabb3fcc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68464 Tested-by:
core-ci <typo3@b13.com>
Tested-by: Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
- 18 Mar, 2021 1 commit
-
-
The SVG Tree class is now a lit element, allowing for further reduction of d3 usage in favor of native HTML5 APIs. Resolves: #93773 Releases: master Signed-off-by:
-
- 15 Mar, 2021 1 commit
-
-
Benni Mack authored
The SVG tree is now building the SVG elements and needed containers ("<g>") via lit-helper. In addition, the update() method is renamed to this.updateVisibleNodes() to easier integrate this as Lit element, as update() is a reserved protected method in lit. The initialize() method is much cleaner, as the event listener registration is now separated in a custom method. Resolves: #93724 Releases: master Change-Id: I945cd620f9900c6ea535dfe5f0d44ee5ced46f89 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68367 Tested-by:core-ci <typo3@b13.com>
Tested-by: Daniel Gorges <daniel.gorges@b13.com> Tested-by:
-
- 11 Mar, 2021 1 commit
-
-
This change optimizes the SVG Tree implementations (again), this time focussing on using proper constructors for SVG tree and its derivatives (SelectTree, PageTree, FileStorageTree). In addition, the search + filter logic is now moved into the base class, in order to reduce duplicate code, and to re-add features (next steps) that were not implemented in TYPO3 v9 when re-writing the page tree, such as highlighting filtered results. In addition, unused properties and settings are removed. This change marks one of the final changes for reworking the SVG Tree implementation, afterwards allowing us to move towards: * native DOM events in favor of d3-dispatch * custom elements instead of wrapper methods * decouple "top." and "document." based settings into the Container classes Resolves: #93701 Releases: master Change-Id: I55733b8c2d0a84ca263ac6e77d7d0bac30877e25 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68332 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 10 Mar, 2021 1 commit
-
-
This patch provides the following changes in order to have better abstractions and encapsulate the dependencies of each implementation. 1. SelectTree (Category Tree) The TreeToolbar is now clearly coupled into the SelectTree and built as LitElement inside the SelectTreeElement. SelectTree now contains all relevant functionality regarding selecting multiple items, and shows settings (SelectTreeSettings) which were only used in SelectTree. This is especially relevant for the multiple item selection, and the exclusiveKey handling. 2. PageTree + FileStorageTree Obsolete public methods are removed, and visibility is changed. Filtering is now separated in favor of a non-public property. By using Types (in e.g. PageTreeDragDrop) the visibility is also adapted Obsolete wrapper methods are removed. Resolves: #93692 Releases: master Change-Id: Ifead098bb80e37d5c7ad5e1d0eabda14aa7087ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/68303 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 01 Mar, 2021 1 commit
-
-
The component is provided as replacement for the current lit-helper `icon()` which cannot provide support for icon usage inside shadow dom elements. The component renders all icons as inline SVGs. FontawesomeIconProvider is therefore adapted to provide inline rendered SVGs for font-awesome icons. Not that these inline font-awesome SVGs will also be used in areas where 'inline' icons are requested (like information toolbar) but the fallback to 'default' was used before. The component supports all properties of the Icon API via HTML attributes. Colors and custom sizes can be applied to the component via CSS color/font-size property: typo3-backend-icon[identifier=status-dialog-information] { color:#6daae0; /* An explicit font-size will be used as icon width & height */ font-size: 1.2em; } Resolves: #93473 Releases: master Change-Id: I3044c325f122eb0085ecb3f45fb9502bfb314d5d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67675 Tested-by:core-ci <typo3@b13.com>
Tested-by:
-
- 19 Feb, 2021 1 commit
-
-
A new API is introduced, providing multi-factor authentication for the Core. The API is furthermore directly used to add two MFA providers by default: * TOTP (time-based one-time passwords) * Recovery codes Even if the API is designed to allow MFA in both, backend and frontend, it is currently only implemented into the backend. Users can therefore configure their available MFA providers in a new backend module, accessible via their user settings. There are also some configuration options for administrators to e.g. define a recommended provider or to disallow available providers for specific users or user groups. Administration of the users' MFA providers is possible for administrators in the corresponding user records. New providers can be introduced by implementing the MfaProviderInterface and tagging the service with the `mfa.provider` tag. Note that the API is currently marked as internal since changes in upcoming patches are to be expected. Following dependencies are introduced: * bacon/bacon-qr-code "^2.0" * christian-riesen/base32 "^1.5" Possible features that could follow later-on: * MFA frontend integration * Webauthn core provider for FIDO2 and U2F. * Forcing users to set up MFA on login * Password-recovery with active MFA Resolves: #93526 Releases: master Change-Id: I4e902be624c80295c9c0c3286c90a6a680feeb5d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67548 Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 10 Feb, 2021 1 commit
-
-
This change splits up Drag+Drop handling in general for SVG-based trees into PageTree specific logic, and common usages. This makes Drag+Drop functionality usable in more places than just the PageTree In addition, all usages of jQuery are removed and proper types were added instead of using "any". Resolves: #93478 Releases: master Change-Id: Ibb17cdd718424760676899b7746cb0828e06fc7d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67682 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 09 Feb, 2021 1 commit
-
-
This change migrates all left-over components of * SvgTree * SelectTree (a.k.a. CategoryTree) * and PageTree to TypeScript adding types in various places to make the code less error-prone. Resolves: #87678 Resolves: #85400 Releases: master Change-Id: Ibb4024d365857c44018a7a201c1cf75baa48179a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67662 Tested-by:
core-ci <typo3@b13.com>
Tested-by:
-
- 04 Feb, 2021 2 commits
-
-
This change aims to reduce the overhead by using jQuery in favor of Vanilla JS in various Tree-related JS files in preparation for a TypeScript migration. * SvgTree.js * SelectTree.js * PageTree.js * PageTreeToolbar.ts * PageTreeElement.ts * TreeToolbar.ts Resolves: #93427 Releases: master Change-Id: I57fc8e66415ea4ab6eaf690d925fbf7670d74284 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67583 Tested-by:
-
Benni Mack authored
This change migrate the TreeToolbar (used in FormEngine Category Tree for example) to TypeScript, removing effectively one RequireJS call and replacing it with a native TypeScript component. Removing the rest of the jQuery will be part of a separate effort. Resolves: #93432 Releases: master Change-Id: I3df66cd1c28d096c0f32982347dbd37c58834e4d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67640 Tested-by:
-
- 07 Jan, 2021 1 commit
-
-
Benjamin Franzke authored
SelectTreeElement makes use of $.param() without importing jquery via requireJS. Instead of adding the missing jquery import, we simply migrate to the native URLSearchParams, as it is available in all supported browsers. Furthermore we avoid decoding the datastructureidentifier json, as it is encoded to json server side. We do this, because URLSearchParams does not url encode nested objects. Resolves: #93200 Releases: master Change-Id: I0da98092da6e09d6576bbdb59112d738086be238 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67323 Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 06 Jan, 2021 1 commit
-
-
The FormEngine field type `selectMutlipleSideBySide` is very special, as it's a combination of four input and select fields. With the refactoring done in #87324 an issue in the validation has been introduced which caused the validation of the wrong field which contains no validation rules. This patch uses the correct field to obtain the validation rules from, now. Another issue is that values of `selectCheckBox` never have been validated as the necessary validation rules were missing. The rules are now appended to the outermost div container. In the same run, minor styling and markup changes were necessary. Resolves: #93191 Related: #87324 Releases: master, 10.4 Change-Id: I7195213a768fa4814eb3ecd81953a500c77ede5d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67317 Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 29 Dec, 2020 1 commit
-
-
Probably since ever, FormEngine validates the whole form when a field changed or an IRRE item got removed. This patch introduces the following changes: - only fields affected by the `change` event get validated - FormEngineValidation.validate() accepts an optional argument to define the container whose fields get validated. If omitted, the whole form is validated. Resolves: #93046 Releases: master, 10.4 Change-Id: I48d2f597c88815ebc0374bb02cf0aed6ac4086fe Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67094 Tested-by:
-
- 20 Dec, 2020 1 commit
-
-
This changes removes the frontend framework Bootstrap 3, and adds Bootstrap 5 beta 1 (we expect Bootstrap 5 final by the time we release TYPO3 v11 LTS). Bootstrap v3 is not supported by the Bootstrap team any longer, so an update is critical for TYPO3 Core. Bootstrap v5 adds a few accessibility improvements as well as flexbox for rendering containers and grids throughout TYPO3 Backend. All JS components are not bound to jQuery anymore, and have been reworked. A lot of HTML/CSS changes happened, which we slowly migrate (and not in a huge change) to TYPO3's templates, in order to keep this change managable. A legacy CSS/SCSS file is added to keep some backwards-compatibility classes to ease the migration for extension developers who have built their own backend modules. Key features of Bootstrap 5: * "rem" instead of "px" is used by default * CSS variables are introduced * Improved bootstrap focus outline styling (buttons / inputs / links) * Simplified grid functionality * use new button color mixin to increase contrast: Primary, Success and Warning Button color is now dark instead of white EXT:styleguide was used as a basis for upgrading to keep compatibility as much as possible, but more changes will be coming in the next few minor releases. Resolves: #92616 Releases: master Change-Id: Iec989f39649b5460b055ec879199faf38e424f2b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66247 Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 03 Dec, 2020 1 commit
-
-
With the introduction of a new datetime picker, the listener for the event `formengine.dp.change` was not attached properly which broke the validation of updated datetime field. The listener is now attached to the datetimer field properly. To avoid introducing jQuery again, the method `FormEngineValidation.markFieldAsChanged` became aware of non-jQuery objects. Resolves: #92913 Related: #91606 Releases: master Change-Id: I3727f362a7d685fdea9bcdf0f1d3b37eca12d424 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66966 Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
- 03 Nov, 2020 1 commit
-
-
Slug fields currently only support slug recreation if the given generator fields are directly visible in the backend. However, this makes it impossible to recreate slugs even if some postModifiers are defined who can take care of successful slug generation. This commit allows slug recreation if at least one postModifier is defined, even if the defined generator fields are not usable for slug generation. Therefore also EditDocumentController was adjusted to not automatically add slug fields to columnsOnly in case postModifiers are defined for this record. Resolves: #89187 Releases: master, 10.4 Change-Id: Ifd50ec106b5b302cea23d37e470eafae840c8993 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61716 Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 31 Oct, 2020 1 commit
-
-
With splitting the FormEngine in smaller parts, a regression has been introduced in the behavior of selectMultipleSideBySide. This select type supports "exclusive values" which are mutually exclusively selectable. However, due to a typo in the fetched (non-existent) data attribute, the whole behavior was broken. This patch fixes the typo. Resolves: #92737 Related: #87324 Releases: master, 10.4 Change-Id: Ice5de95c49d81df94ee1a8257ecab3abfe7d21d7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66361 Reviewed-by:
Susanne Moog <look@susi.dev> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by: Daniel Goerz <daniel.goerz@posteo.de> Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Riccardo De Contardi <erredeco@gmail.com> Tested-by:
-
- 19 Oct, 2020 1 commit
-
-
Christian Kuhn authored
The 'Make textareas resizable' setting is quite ancient. The patch drops this option from the user settings and enables 'growing' text areas by default. To prevent text areas from growing indefinitely, the user setting 'max height' with a default of 500px is kept. Change-Id: I0497c6823b96b077c05d25a2e63ae58c079400b7 Resolves: #92582 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66162 Tested-by:
-
- 16 Oct, 2020 1 commit
-
-
Andreas Fernandez authored
This patch replaces the bootstrap-datetimepicker with flatpickr which is pretty lightweight. Since this datetimepicker also has some sanity validation on board, much custom datetime parsing in FormEngine can and has been removed, including magic date manipulation by using addition or subtraction. The year format for momentjs has been changed from `YYYY` to `Y` as well to support years < 1000. Currently the datepicker is not able to select a date < 100. By manual selection, the picker jumps back to 1999 and not to 99 as expected. Resolves: #91606 Releases: master Change-Id: Id723c5200c797019f6de0ed5a4c15b2137a32995 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64833 Tested-by:
-
- 10 Oct, 2020 1 commit
-
-
This patch removes jQuery from a major part of FormEngine components, including elements, field wizards, enhancers and IRRE. Additionally, the argument `optionEl` of the method `FormEngine.setSelectOptionFromExternalSource()` accepts objects of type `HTMLOptionElement` which renders jQuery objects obsolete, which has been deprecated. Resolves: #91911 Releases: master Change-Id: I5b7d2f4c7b9b5993a5bbe8cec016aa74cabbbecd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65009 Tested-by:
Stefan Froemken <froemken@gmail.com> Tested-by:
-
- 08 Aug, 2020 1 commit
-
-
This changes the configuration of the TypeScript compiler to resolve modules in "node" style, which allows using TypeScript declaration files (*.d.ts) shipped with npm packages. Additionally the option "esModuleInterop" is enabled which allows us to use CommonJS modules in AMD modules without fiddling with incompatible exports. As a negative side-effect, all JavaScript have to get recompiled to reflect these changes. Resolves: #91954 Releases: master, 10.4 Change-Id: If6386f5062bfbe439615bb947e94cd728dfd5b2b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65225 Tested-by:
-
- 20 Jun, 2020 1 commit
-
-
Andreas Fernandez authored
Some modules have been rewritten to not use jQuery in the past. However, there was still a dependency due to missing `ready` handling. Since recent changes TYPO3 is capable of such handling and enables to remove jQuery completely from some modules. Resolves: #91598 Releases: master Change-Id: I23fa63f9090eee8abc49cd1993df27bec12d92e2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64832 Tested-by:
-
- 09 May, 2020 1 commit
-
-
It's safe to use getElementById() instead of querySelector() in case an element is fetched by its ID. Numbers for nerds: getElementById() is nearly 1.5x faster than querySelector(). To be fair, both functions are really fast with executing multiple million operations per second, thus nobody will notice a performance impact. See https://www.measurethat.net/Benchmarks/ShowResult/106740 Resolves: #91254 Related: #91183 Releases: master Change-Id: I2ed590d20c9af66ce818f012ac73ec45c5c9fa55 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64384 Tested-by:
-
- 18 Apr, 2020 1 commit
-
-
Christian Eßl authored
Resolves: #91103 Releases: master Change-Id: If342b9bf69574b54d598e342c3bb2773dba582cb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64224 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by: Jonas Eberle <flightvision@googlemail.com> Reviewed-by:
Christian Eßl <indy.essl@gmail.com> Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by:
-
- 03 Feb, 2020 1 commit
-
-
If slugs are generated within Backend forms, the visual output (= label below slug field) of the generated slug proposal might be broken if no slash is prepended to the generated slug. This might be the case in custom database tables where custom slug fields are defined with the configuration "prependSlash" set to "false" (which is the default value). It can also be the case if the configuration "prefixParentPageSlug" is set to "false". In order to ensure a clean visual output for those labels, the slug proposalwithin them will now always be prepended by a slash. This makes sure that the resulting url which is shown within those labels is always valid. Note that this only effects visual output and is not meant to modify any slug proposal generated by the SlugHelper class. Resolves: #90222 Releases: master, 9.5 Change-Id: I93587cfec0db6c3d889fdce60a4515ef47decc82 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63051 Tested-by:
theline <typo3@theline.capella.uberspace.de> Tested-by:
-
- 02 Feb, 2020 1 commit
-
-
Andreas Fernandez authored
The AJAX API doesn't expose the AbortController anymore as it has no benefit for a developer, besides aborting a request. For this reason, the AJAX API removes the `getAbort()` method and replaces it with an `abort()` method, which utilizes the controller directly. Resolves: #90292 Releases: master Change-Id: Id6355663bc00bbb763692ca3b7fab145cb8cc55e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/63141 Tested-by:
-
- 17 Jan, 2020 1 commit
-
-
Andreas Fernandez authored
This patch replaces the usages of `$.ajax()` and its friends with the AJAX API provided by TYPO3 Core. Resolves: #90038 Releases: master Change-Id: Ief3767dd5a5256dca269b8dfb496f37a9bcdbe69 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62790 Tested-by:
Jörg Bösche <typo3@joergboesche.de> Tested-by:
Steffen Frese <steffenf14@gmail.com> Tested-by:
Henning Liebe <h.liebe@neusta.de> Tested-by:
Tobi Kretschmann <tobi@tobishome.de> Reviewed-by:
-
- 09 Nov, 2019 2 commits
-
-
This commit adds an option to the slug input type which allows it to use the uid of a record when the update slug button is pressed in the FormEngine. Resolves: #89560 Releases: master, 9.5 Change-Id: Id645714f1b26e20e511022d1c74ea793964ffa19 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62170 Reviewed-by:
Daniel Sattler <sattler@b13.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by: Wolfgang Klinger <wolfgang@wazum.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: -
Dynamically fetching/applying additional data for the link explanation seems to be overdone, so we simply deactivate the toggle button and remove the icon after selection/modification of the link target. After persisting the record, the updated link explanation will be visible. Resolves: #88737 Releases: master, 9.5 Change-Id: I679abb2178aedfc8a29cccace99950a3a8acaab6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61422 Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Alexander Stehlik <alexander.stehlik@gmail.com> Tested-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 07 Nov, 2019 1 commit
-
-
The InputDateTimeElement now takes an element identifier to initialize a field as a date time picker. The DateTimePicker module now uses an optional element identifier to render the date time picker. Resolves: #89586 Related: #87324 Releases: master Change-Id: I65727fe503fed65b28e38f64b1a44b619087b937 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62197 Tested-by:
-
- 25 Sep, 2019 1 commit
-
-
TSLint is in a deprecation phase, recommending to migrate to ESLint instead. This patch removes all TSLint packages and supplies a proper ESLint configuration. Also, rule violations are fixed in this patch. Executed commands: yarn add --dev typescript-eslint \ @typescript-eslint/parser \ @typescript-eslint/eslint-plugin \ eslint grunt-eslint yarn remove tslint grunt-tslint ./node_modules/.bin/eslint -c eslintrc.js --fix --ext .ts \ ./Sources/TypeScript/ Resolves: #89232 Releases: master Change-Id: I3bd4a1c30ecc27f8c334951547aff5e9352629da Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61784 Tested-by:Frank Nägler <frank.naegler@typo3.org> Reviewed-by:
-
- 23 Sep, 2019 1 commit
-
-
Since the build chain can generate ES6, the TypeScript code should incorporate these changes. Namely, this patch changes: - Use native NodeList over arrays generated by Array.from() where possible - Use explicit string search functions instead of indexOf Resolves: #89118 Releases: master Change-Id: I6e03ade35c545ece05ecca222cd1fde876fc22d4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61649 Tested-by:
-
- 07 Sep, 2019 1 commit
-
-
To ease the upgrade to TypeScript 3.6, this patch adjusts the source code in a TS 2.4 compatible way. This way, the upgrade patch stays as small as possible. Resolves: #89106 Releases: master Change-Id: I7e2d65262395e19f958182f8658aa326dd0aec43 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/61638 Tested-by:
-
