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 .
  1. 28 Jul, 2021 1 commit
  2. 21 Jul, 2021 1 commit
  3. 20 Jul, 2021 1 commit
  4. 12 Jul, 2021 2 commits
  5. 09 Jul, 2021 2 commits
  6. 29 Jun, 2021 3 commits
  7. 14 Jun, 2021 1 commit
  8. 11 Jun, 2021 1 commit
  9. 10 Jun, 2021 1 commit
  10. 08 Jun, 2021 1 commit
    • Oliver Bartsch's avatar
      [FEATURE] Simplify sharing of backend urls · 24f43811
      Oliver Bartsch authored and Benni Mack's avatar Benni Mack committed
      Atfer a lot of preperation in #93048 and #93988,
      it's finally possible to share URLs to TYPO3 backend
      modules. Even special modules such as FormEngine.
      
      To ease the use for editors, the ShortcutButton
      is extended for a new option. If enabled, which
      is the default behaviour, the shortcut button
      in the module header is replaced. The new button
      allows to open a dropdown with the additional
      possibility to copy the URL of the current
      page to the operating systems' clipboard. Next
      to the already exisiting "Add shortcut" option.
      
      Since those URLs should not contain the user
      specific token, the UriBuilder features a new
      constant "SHAREABLE_URL". If set as $referenceType
      in one of the supporting methods, e.g. buildUriFromRoute(),
      an absoulte URL without the token is returned.
      
      To copy the URL to the operating systems' clipboard,
      a new web component "CopyToClipboard" is introduced.
      This component is added without any dependency to
      the URL sharing functionality and can therefore be
      freely used for other backend components as well.
      
      For the new button, the font awesome "share-alt"
      icon is registered in the IconRegistry.
      
      Resolves: #93921
      Releases: master
      Change-Id: Id1dcfe1f2af764fbe000659ddb49a7369322d5b6
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69338
      
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Jochen's avatarJochen <rothjochen@gmail.com>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Reviewed-by: Jochen's avatarJochen <rothjochen@gmail.com>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      24f43811
  11. 07 Jun, 2021 1 commit
  12. 01 Jun, 2021 2 commits
  13. 30 May, 2021 1 commit
  14. 27 May, 2021 1 commit
  15. 26 May, 2021 1 commit
    • Richard Haeser's avatar
      [TASK] Set proper title of window in backend · 2cba0bac
      Richard Haeser authored and Benjamin Franzke's avatar Benjamin Franzke committed
      With the introduction of the new backend module web component router,
      the title of the backend windows will be set to the title of the
      main iframe. Most of the modules didn't provide a proper name though.
      
      For most modules we have a proper name now which will show up in the
      title of the backend window, if no title is propagated by the module,
      the backend router will fallback to the default backend title.
      
      As the format of the title is quite "personal". If you are used to have
      opened more TYPO3 backend windows, you would like to see which
      installation you have open. If you only work in one backend, you
      might want to see on which module you are currently working. It is
      possible to set the order of the title of the backend within your
      user settings now. By default it will be title - siteName [version]
      
      Resolves: #94182
      Releases: master
      Change-Id: I02602650370140217aa252bbd8e29ea4e05d994a
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69172
      
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Jochen's avatarJochen <rothjochen@gmail.com>
      Tested-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      Reviewed-by: Jochen's avatarJochen <rothjochen@gmail.com>
      Reviewed-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      2cba0bac
  16. 19 May, 2021 1 commit
    • Benjamin Franzke's avatar
      [TASK] Streamline spinner web component size and animation · 1cfbf51a
      Benjamin Franzke authored
      This change performs the following optimizations:
      
      * Detach spinner from content flow using a relative+absolute
        position normalization, allowing an equivalent positioning
        to the regular backend icons.
        This is to ensure that both, <typo3-backend-spinner> and
        <typo3-backend-icon> render equally when used in inline(-block)
        containers (for example .svg-toolbar__drag-node).
        <typo3-backend-spinner> used to cause vertical alignment offsets,
        when the spinner was positioned in inline text-flow and therefore
        caused the vertical flow to cause offsets.
      
      * Add a variant="light|dark" attribute to select
        between the available TYPO3 spinner variants.
        By default the current color is now used.
      
      * Adapt sizing to inherit size from current font-size when used
        without a specific size attribute. Also apply that to the
        backend icon component to stay interchangeable.
      
      * Render spinner via SVG and only animate the spinning part
        instead of the entire shape. This is to avoid the bouncing-icon
        effect that CSS animations on the entire element cause
        (as often seen with font-awesome spinners for example).
      
      Releases: master
      Resolves: #94149
      Change-Id: I00d2e4915a0644726f78abe485fd9e276b539259
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/69162
      
      Tested-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      Reviewed-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Reviewed-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      1cfbf51a
  17. 17 May, 2021 1 commit
  18. 14 May, 2021 2 commits
  19. 13 May, 2021 2 commits
  20. 11 May, 2021 1 commit
  21. 03 May, 2021 2 commits
  22. 02 May, 2021 1 commit
  23. 01 May, 2021 2 commits
  24. 30 Apr, 2021 1 commit
    • Benjamin Franzke's avatar
      [FEATURE] Introduce backend module web component router · de74be87
      Benjamin Franzke authored
      A custom Lit-based web componenent router is added which
      reflects module URLs into the browser adress bar and
      at the same time prepares for native web components to
      be used as future iframe module alternatives.
      
      Such modules will be implemented as JavaScript modules,
      that provide an implementation for a custom HTML Web
      Component. The first of such components (added within
      this change) is a wrapper component for traditional
      iframe-based backend modules.
      
      Module state changes are advertised via DOM events and
      propagated to the browser address bar, browser title,
      and the module menu.
      
      Adress bar updates
      ==================
      
      The module URL to address bar synchronisation enables sharable
      module deeplinks to be copied from the browser address bar.
      Whenever a component advertises a state change (e.g.
      iframe change), a sharable deep link is generated and
      shown in the browser adressbar.
      
      Technical preparation for the required deeplinking has been
      added with #93674.
      
      History Management
      ==================
      
      Browser history state is managed via the iframe
      history context of the content module frame
      (that is unlike other modern Single Page Applications
      which use history.pushState and history.replaceState).
      
      This approach required some synchronisation work, but there are
      technical limitations that prevent a combination of iframe history
      updates in combination for newer API like history.pushState.
      (The limitation is: state added by history.pushState is skipped
      by iframe history handling).
      
      The advantage of this compromise is: All "traditional" modules will
      preserve their state handling as before, no breaking/behavioral
      changes for iframe-based modules.
      
      Routing
      =======
      
      The router uses two parameters to perform routing:
       * module – Module name as defined in ext_tables.php
       * endpoint – (json) api to be used by the component (= module URL)
      The module attribute is used to perform the actual routing
      to the respective backend module component, while the endpoint
      attribute serves as API to parse/fetch the state of the module.
      
      A named slot is used to switch between the available module components.
      That means only one of the routers childNodes will be visible at a
      time, while all modules are actively attached to the DOM.
      State is therefore preserved when switching between modules
      and the iframe is always kept active, allowing to act as history
      state-container (as described in "History Management").
      
      Example of two modules that are attached to the DOM, where
      only <typo3-configuration-module> is visible as the <slot>
      in the shadow root puts a reference to this childNode:
      
      <typo3-backend-module-router module="system_config" endpoint="…">
        #shadow-root
          <slot name="TYPO3/CMS/Lowlevel/ConfigurationModule"></slot>
        <typo3-iframe-module endpoint="…"
          slot="TYPO3/CMS/Backend/Module/Iframe"></…>
        <typo3-configuration-module endpoint="…"
          slot="TYPO3/CMS/Lowlevel/ConfigurationModule"></…>
      </typo3-backend-module-router>
      
      Note: The "TYPO3/CMS/Lowlevel/ConfigurationModule" component is not
      yet part of this commit, and only serves as an example (will be
      implemented later on). The slot name is resolved from
      the module key.
      
      Out of scope for this patch (will follow later)
      ===============================================
      
       * Link based routing interception via data-module tag for anchor tags.
         To be added as an additional convenience API on top of the
         router module and endpoint attribute (current API).
       * Convenience components for module layout
       * Integration into shortcut handler
       * Install-tool URLs do not reflect into addressbar right now
         Install-tool modules are redirected, therefore url updates can not
         be mapped as backend URLs right now
         Solution will probably be to integrate the install tool
         components as web component into the backend.
      
      Resolves: #93988
      Related: #93674
      Releases: master
      Change-Id: I682e89649b597c8c74b6a0a8f198f6bcf5bbc347
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67464
      
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Tested-by: Andreas Fernandez's avatarAndreas Fernandez <a.fernandez@scripting-base.de>
      Tested-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      Reviewed-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Reviewed-by: Andreas Fernandez's avatarAndreas Fernandez <a.fernandez@scripting-base.de>
      Reviewed-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      de74be87
  25. 27 Apr, 2021 1 commit
  26. 23 Apr, 2021 3 commits
  27. 22 Apr, 2021 1 commit
  28. 20 Apr, 2021 2 commits