Issue Bug Closed

#94194Linkbrowser in Ckeditor: Automatic changing of title and target when selecting a class isn't working with 9LTS anymore

Jennifer Hauß 05/25/21, 13:37 updated 04/03/25, 11:57

Description

Hey folks,
When updating a project from 8LTS to 9LTS I came across a change in behaviour in the linkbrowser of the ckeditor. With 8LTS it was possible to change the title and target automatically when a class is selected.
This isn’t working with 9LTS anymore.

Setup looks like this:

classesAnchor:
    internalLink:
        class: 'internal-link'
        titleText: 'Öffnet einen internen Link im aktuellen Fenster'
        type: 'page'
    internalLinkNewWindow:
        class: 'internal-link-new-window'
        titleText: 'Öffnet einen internen Link in einem neuen Fenster'
        target: '_blank'
        type: 'page'
    externalLink:
        class: 'external-link'
        titleText: 'Öffnet einen externen Link im aktuellen Fenster'
        type: 'url'
buttons:
    link:
        relAttribute:
            enabled: true
        targetSelector:
            disabled: false
        properties:
            class:
                allowedClasses: 'internal-link,internal-link-new-window,external-link'
classes:
    'internal-link':
        name: 'Interner Link'
    'internal-link-new-window':
        name: 'Interner Link neues Fenster'
    'external-link':
        name: 'Externer Link'

Also the default value for the title isn’t set anymore.
The title changes with selecting of a class though if the option

buttons:
  link:
    properties:
      title:
        readOnly: true

is set.
Is this a wanted change in behaviour or a bug?

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 3

  1. Georg Ringer commented and changed status New Closed <span data-processor="relativetime" data-value="2025-04-03T11:57:56+00:00" > 04/03/25, 11:57 </span>

    closing this very old issue. yes the automated title has been removed as it makes no sense accessibility vise to fill the web with duplicated content. it must be filled manually (or at least with good knowledge) and not just with same string over and over. this could happen in the frontend as very last fallback but should not be in the db