Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • T TYPO3.CMS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • accessibilityaccessibility
  • TYPO3.CMS
  • Repository
Switch branch/tag
  • TYPO3.CMS
  • ..
  • Container
  • InlineControlContainer.ts
Find file BlameHistoryPermalink
  • Andreas Fernandez's avatar
    [BUGFIX] IRRE: Handle localizable records correctly · c29f21e4
    Andreas Fernandez authored Aug 06, 2020 and Anja Leichsenring's avatar Anja Leichsenring committed Aug 25, 2020
    Each node in an IRRE container now has a new `data-placeholder-record`
    attribute to be able to identify such node w/out accessing CSS classes
    used for styling purpose.
    
    Nodes where `data-placeholder-record` has a truthy value are localizable
    and are ignored now when the sorting is changed which solves an issue
    where such records would have been moved into a different language.
    
    In the same run the localization is fixed as it was tried to iterate an
    object, which doesn't work. Alternatively, the object values are fetched
    and iterated now.
    
    Resolves: #91942
    Resolves: #91938
    Releases: master, 10.4
    Change-Id: Ic6622eb5d6950893f79d4ae9697d7eaa096d2ef9
    Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65214
    
    
    Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
    Tested-by: default avatarTYPO3com <noreply@typo3.com>
    Tested-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
    Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
    Reviewed-by: Anja Leichsenring's avatarAnja Leichsenring <aleichsenring@ab-softlab.de>
    c29f21e4