adobe / adobe/aem-core-wcm-components

Issue with XF component Dialog after SDK Upgrade

Open
#2,471 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
796
Forks
776
Avg merge
3d 22h
Merged PRs (30d)
8

Description

## Bug Report

**Current Behavior**

Issue with XF component's dialog , XF path browse field's forward slash “/” for content is missing and have a white space. We also noticed that there is a new trailing slash after master.
The value is getting saved correctly in CRX for XF path property. We noticed these differences after the AEM Cloud SDK upgrade to version 2023.2.11289.20230224T170559Z

**Expected behavior/code**

XF component's dialog, XF path browse field to start with forward slash "/" and no white space . Also no forward slash after master.

**Environment**
- AEM as Cloud Service 2023.2.11289.20230224T170559Z
- Core Components version -2.21.2 , bundle location- launchpad:resources/install/20/core.wcm.components.core-2.21.2.jar
- JDK 11

**Screenshots**
**After SDK Upgrade**
![XF Dialog with SDK Upgrade](https://user-images.githubusercontent.com/129329932/228856118-ae7fe79e-5cfd-475a-8e4d-d4d3f73a3b7a.png)
**Before SDK Upgrade**
XF Dialog without SDK Upgrade

Contributor guide

Open the contributing guide

Research direction

Reproduce the XF component dialog path-browser behavior on AEM as Cloud Service SDK 2023.2.11289.20230224T170559Z and compare it with the provided before/after screenshots. Trace the dialog and XF path field behavior in Core Components 2.21.2; the issue is done when the displayed path has the expected leading slash, no whitespace, and no trailing slash after master while the saved CRX value remains correct.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.