Fields in XDP - 6.1 vs 6.5 - floating or not? | Community
Skip to main content
crich2784
Level 6
May 27, 2025
Solved

Fields in XDP - 6.1 vs 6.5 - floating or not?

  • May 27, 2025
  • 1 reply
  • 613 views

I have a customer form that is being rendered in 6.1 and the fields appears to be behaving like floating fields.  You can see the below picture that the <period> is flush against the word SCRUBBED12.  

 

 

The same XDP rendered in 6.5 is as expected - fixed width.

 

You can see in Designer, it is not a floating field.  It is a Text Field overlaid on to Static Text.

 

What is unusual is that UNDER the field is the following static text.

 

I have never seen this.  Is this some notation for floating fields?

 

Thanks,

Charles

 

 

 

Best answer by sudhansh

Hi @crich2784 ,

Could you confirm is you have enabled mfDataDependentFloatingField on the profile as captured here in scripting section:
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/html5-forms/faq

Hopefully it should resolve the issue for you.

1 reply

crich2784
crich2784Author
Level 6
May 27, 2025

Ok, I found that this is a legacy/deprecated notation for floating fields - awesome that I know the problem.  Now the problem is that they use the fields in HTML5 to modify the data and floating fields are not interactive in HTML5 - ugh.  Anybody have any ideas for a workaround, that would be great.

sudhansh
Adobe Employee
sudhanshAdobe EmployeeAccepted solution
Adobe Employee
May 28, 2025

Hi @crich2784 ,

Could you confirm is you have enabled mfDataDependentFloatingField on the profile as captured here in scripting section:
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/html5-forms/faq

Hopefully it should resolve the issue for you.

crich2784
crich2784Author
Level 6
May 28, 2025

Yes, I found that flag and enabled it.  Floating fields are now working.

 

The real problem is an "interactive" floating field.  In the PDF world, they were able to overlay and interactive field and the "#f1#            #" notation allowed it to be a fixed size during interaction.  When sent for output, the paragraph would flow correctly.  Unfortunately, I can't duplicate this functionality in HTML5 so there will be a compromise with the customer.