@del65008 : this is already logged and will be prioritized.

@raviranjan : please validate if the DITA Profile (Tools > Guides > DITA Profile)  has all the catalogs added in the correct order.  Please also share a screenshot of DITA Profiles.  

@Sadaykumar : is this query related to AEM Site pages generated from AEM Guides?

@sschnelbach : I assume by "file title" you mean the "Title" property in the metadata of the asset. Those properties are extracted from the XML content (<title> element), as you observed correctly. And in current behavior that title property is used to display the title of the file in various interf...

@raviranjan : please also check: - The reports tab, if it reports any errors with the references in the map - the output presets tab, whether all the expected output types are showing up?   Please also share the ditamap source - for us to assess what could be wrong.

@suresh_36 : which version of AEM Guides are you currently trying this with? Also, can you confirm if the link component is overlay'd or OOTB?

@ravir73578276 : This has to be custom built. OOTB there is currently no path to get SPA directly.

@MayurSatav : It depends on what elements/attributes of DITA topic do you plan to map to the tab component properties. Basically when you map a element to a AEM component, the DITA element should have enough sub-elements/attributes that are expected by the component code (sightly/jsp) or else you wi...

@sschnelbach @BRG_MA : do you already have a support ticket for this? (I assume both of you are from same team)Please send out a note to the Customer Success Manager on this - we would like to understand this further.

So is the above behavior reproducible on Chrome as well then?In the mean time - I tried the same on edge as well and I didn't face the slowness - however I did not work whole day on the editor.Also, with your last post - is it safe assumption that this behavior is not content specific?