Project

General

Profile

Actions

Feature #104479

open

Add possibility to customize pre-selected target values/options in LinkBrowser

Added by Moritz Ngo 4 months ago. Updated 4 months ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2024-07-25
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
LinkBrowser
Complexity:
easy
Sprint Focus:

Description

It would be a great addition to the usability of TYPO3 CMS' LinkHandler, when the pre-selected target values/options can be customized.
Currently it's only possible to select from the values/options "Top"[_top] and "New Window"[_blank], which are hard-coded in the following classes/methods:

Here are some user stories that'll describe several use-cases:

  1. As a backend user , I want to select customized pre-selected target values/options in the LinkBrowser.
  2. As a TYPO3 CMS Integrator , I want to configure the pre-selected target values/options of the LinkBrowser via TsConfig.
  3. As a TYPO3 CMS Developer , I want to manipulate the pre-selected target values/options of the LinkBrowser via a PSR-14 Event.

Files

Actions #1

Updated by Moritz Ngo 4 months ago

  • Description updated (diff)
Actions #2

Updated by Moritz Ngo 4 months ago

  • Description updated (diff)
Actions #3

Updated by Garvin Hicking 4 months ago

  • Status changed from New to Needs Feedback

Could you maybe describe the use case for this? I only remember targets other than the hardcoded ones from the "dark ages of framesets", so I'd be curious where this could be used. :-)

Actions #4

Updated by Garvin Hicking 4 months ago

  • Category set to Site Handling, Site Sets & Routing
Actions #5

Updated by Moritz Ngo 4 months ago

A common use-case would be somthing like a lightbox or modal box.

In my particular case, I needed the value "Overlay"[overlay] and added a patch-file which adds a new hard-coded option :P

Actions #6

Updated by Garvin Hicking 4 months ago

Ah, thank you.

I wonder though, could you just use CSS classes and predefined ones, and then have your javascript that spawns modals/lightboxes react based on class name instead of target-attribute?

This would of course be a workaround. I think if a target list gets changeable it would need to be inplemented to all of: Typoscript configration, yaml configuration, TCA definition (like the other fields), which is a bit of work. ;)

Actions

Also available in: Atom PDF