Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

JoniVanderheijd
Community profile JoniVanderheijd Level 2
Job title here
Location here
5 BADGES
Level 2

Level 2

Learn more
Joined the community 13-06-2018 10:15:11 PM
Offline
Top badges earned by JoniVanderheijd
Customize the badges you want to showcase on your profile
Re: Default value not being displayed after upgrade to AEM 6.3 SP2
Avatar
Give Back 3
Level 2
JoniVanderheijd
Level 2

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
JoniVanderheijd
- Adobe Experience Manager
Hello Alistair,Adobe came back to us that this change was intentional and this is behavior as expected.We implemented a work-around by overwriting these two files:granite/ui/components/foundation/form/field/init.jspgranite/ui/components/coral/foundation/form/field/init.jsp… String value = cmp.getValue().val(cmp.getExpressionHelper().getString(cfg.get("value", ""))); // START - Work-around for default value bug if (value == null) { value = cmp.getExpressionHelper().getString(cfg.get("value", ""))...

Views

4.8K

Like

1

Replies

2
Re: Default value not being displayed after upgrade to AEM 6.3 SP2
Avatar
Give Back 3
Level 2
JoniVanderheijd
Level 2

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
JoniVanderheijd
- Adobe Experience Manager
Thank you, we created a ticket.

Views

4.8K

Likes

0

Replies

4
Default value not being displayed after upgrade to AEM 6.3 SP2
Avatar
Give Back 3
Level 2
JoniVanderheijd
Level 2

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
JoniVanderheijd
- Adobe Experience Manager
We're upgrading to AEM 6.3 SP2, and we noticed something strange.The default value for textfield input fields we use in authoring dialogs is no longer displayed.We define our components like this: I've traced the issue to this line of code in the initialization of the field super type: (/libs/granite/ui/components/coral/foundation/form/field/init.jsp) String value = cmp.getValue().val(cmp.getExpressionHelper().getString(cfg.get("value", "")));I did some debugging:- cmp.getExpressionHelper().getS...

Views

5.9K

Like

1

Replies

6
Re: Start z-index for overlays
Avatar
Give Back 3
Level 2
JoniVanderheijd
Level 2

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
JoniVanderheijd
- Adobe Experience Manager
Thanks, This replaced the popover container with a coral3-Popover which handles his layering better. It had a z-index of 10020.This was actually the first thing I tried, but didn't seem to work. I was probably still hitting an old version of the component.

Views

666

Likes

0

Replies

0
Start z-index for overlays
Avatar
Give Back 3
Level 2
JoniVanderheijd
Level 2

Likes

2 likes

Total Posts

5 posts

Correct reply

0 solutions
Top badges earned
Give Back 3
Give Back
Ignite 1
Validate 1
Boost 1
View profile
JoniVanderheijd
- Adobe Experience Manager
We're doing some testing on AEM 6.3 SP2, and I stumbled on an issue in one of our screens. To edit a component we open a modal foundation form which gets opened in a coral-dialog overlay. In that modal menu we have a foundation datepicker component which opens in a coral-popover.The issue is the datepicker appears behind the modal menu, because the coral-dialog has a z-index of 10010 and the coral-popover has a z-index of 1480.Diving into the Coral UI 2 javascript I noticed the start z-index for...

Views

902

Likes

0

Replies

3
Likes given to
Likes from