Thanks daitienshi​,I added a sling internal redirect, to handle request matching e.g. localhost.4503/$.  While the mapping worked ok when accessing the publish instance directly, i.e. http://localhost:4503 internally redirects as i'd hope to, when accessing via apache/dispatcher the dispatcher logs ...

daitienshi, @Jorg Did this get resolved? I'm seeing similar.

Thanks Hemant Arora​Unfortunately I had already tried most of the suggestions on the decoration-tag page.  I still have an unwanted <cq> tag I can't seem to hide and which contributes to our issue.1. cq:noDecoration affected my parsys such that adding content items results in them being added as sib...

Hi,we are developing - with AEM 6.3 - some custom Sightly authoring components, which integrate some vue.js code. When adding content under a parsys (foundation/components/parsys/new) and parsys/new, the markup is decorated (?) with <cq> elements.  So if we add a content item (in our case a 'card') ...

Sorry Promilag - no update from me.  I didn't follow the solution marked above as my page templates are built with jsp, so i left the sightly js using currentDesign.getJSON() to get the required values.

Thanks your help @Feike.Yes, I realise Sightly is server-side.  This is probably to do with me producing bad markup that is then automatically corrected by the browser:  I have an anchor with lots of html elements inside it and presumably at some point Chromium decides that's malformed html and inse...

UPDATE Now I'm very confused! : turning on/off javascript in the browser results in different markup in the DOM, including inclusion/ exclusion of the additional div (<div class="help-category">) added by AEM.  (This additional div is in the raw HTML but not in the DOM when javascript is turned off)...

Hi, thanks for the reply and help @leeasling.Yes, apologies in editing my snippet lines (as well as missing quotes in the join clause, correction, the single quotes in the join clause are there - they just look like double quotes in my forum post) I didn't copy the href, should have been more like,<...

I am seeing some unexpected markup generated from 2 sightly files.The Sightly file that includes data-sly-resource and the included Sightly file render ok, until a <ul> element is appears in the included resource markup.  After that, repeated unwanted <a> markup elements are generated that include n...

Many thanks both for the replies.  I've found, read and used all the pages linked to above.My question arises from the following development scenario:I am authoring some javascript 'backing' a Sightly html file. I want to work with properties of the current node (in javascript) as well as its ancest...