Bug fix: fragment block should include fragment classnames [HTML DOM …

[ujjwal5]

…change]

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):

Fix #409

Test URLs:

• Before: https://main--com--ancestry.aem.live/en/
• After: https://fragment-block-fix--com--ancestry.aem.live/en/

[ujjwal5]

Currently, the styles applied to a 'fragment' block are lost when the HTML is replaced. Ideally, any styles defined for the block should be retained. Additionally, the HTML structure of the fragment block is different from other blocks. Normally, the structure follows the pattern: container → wrapper → block. However, for the fragment block, it follows container → wrapper, omitting the block level.

HTML structure with existing code:

<div class="section fragment-container" data-section-status="loaded" style="">
   <div class="fragment-wrapper">
      <div class="section" data-section-status="loaded" data-key="value" style="">
         <div class="default-content-wrapper">
            <p>Would you like to see what you can discover about your family?</p>
            <ul>
               <li>Yes</li>
               <li>No</li>
               <li>I’m not sure</li>
            </ul>
            <p class="button-container"><a href="https://www.ancestry.com/onboarding/lop/questionnaire/intro" title="Continue" class="button">Continue</a></p>
            <p class="button-container"><a href="#" title="Dismiss" class="button">Dismiss</a></p>
         </div>
      </div>
      <div class="section columns-container" data-section-status="loaded" data-key5="value5" style="">
         <div class="default-content-wrapper">
            <p>Another section starting here.</p>
         </div>
         <div class="columns-wrapper">
            <div class="columns style-class block columns-2-cols" data-block-name="columns" data-block-status="loaded">
               <div class="bg-color-1">
                  <div class="text-content">
                     <p>key10</p>
                  </div>
                  <div class="text-content">
                     <p>value10</p>
                  </div>
               </div>
            </div>
         </div>
      </div>
   </div>
</div>

Proposed HTML structure with fixed issues:

<div class="section fragment-container" data-section-status="loaded" style="">
   <div class="fragment-wrapper">
      <div class="fragment animate block" data-block-name="fragment" data-block-status="loaded">
         <div class="section" data-section-status="loaded" data-key="value" style="">
            <div class="default-content-wrapper">
               <p>Would you like to see what you can discover about your family?</p>
               <ul>
                  <li>Yes</li>
                  <li>No</li>
                  <li>I’m not sure</li>
               </ul>
               <p class="button-container"><a href="https://www.ancestry.com/onboarding/lop/questionnaire/intro" title="Continue" class="button">Continue</a></p>
               <p class="button-container"><a href="#" title="Dismiss" class="button">Dismiss</a></p>
            </div>
         </div>
         <div class="section columns-container" data-section-status="loaded" data-key5="value5" style="">
            <div class="default-content-wrapper">
               <p>Another section starting here.</p>
            </div>
            <div class="columns-wrapper">
               <div class="columns style-class block columns-2-cols" data-block-name="columns" data-block-status="loaded">
                  <div class="bg-color-1">
                     <div class="text-content">
                        <p>key10</p>
                     </div>
                     <div class="text-content">
                        <p>value10</p>
                     </div>
                  </div>
               </div>
            </div>
         </div>
      </div>
   </div>
</div>

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/en/
🖥️	/en/

[kptdobe]

This PR removes the content of fstab.yaml. Please create a proper PR if this is something to be reviewed.

[ujjwal5]

@kptdobe I had raised this PR almost a month ago, but while testing Config Service APIs on the same repo, they were inadvertently included in this PR. I’ve now raised a new PR (#434) addressing the attached issue.