So do what was mentioned about using the 'version' menu - you need to use the crx explorer, not crx de.

gauravb10066713​ - we just fired up a fresh copy of 6.4.0 and tab.click.js looks like it does in our 6.4.2 version - I'm pretty sure that this won't work with CoralUI3 without the way the one you have looks...

gauravb10066713​ - I didn't apply a breakpoint, because it never gets there as the binding action is different; it never binds to the tab with the code we have. We're running 6.4.2; so I'm wondering if this isn't fixed in 6.4.3...

gauravb10066713​ - So my tab.click.js looks different... see below... What version of AEM did you pull that from? It seems concerning that it's different and it seems likely that this is the reason we're seeing the issue we're seeing...Thanks!tab.click.js code:     /**     * Handler to show/hide the...

So - We're working on an AEM 6.4 upgrade project coming from AEM 6.2. I did the work to upgrade our configurations and such to get everything working and we've updated our dialogs to coral3, but it seems that now when you switch to either the blueprint tab or the livecopy tab (depending on the page)...

Handling this on the front end is incorrect, IMHO because it'll cause a shift in layout as the page loads. It's worthwhile to note that this is mainly an issue in the author because we don't display the wrappers on the publisher and on; so given that, I guess we could use JS to 'shim' this for the a...

So - we don't use Bootstrap; but that being said, most grid systems rely on parents and children to define a containerThis is how most systems work:<div class="grid"> = could be 100% width of the page     <div class="row-6">This is a six column row</div> = could be 50% width of the row     <div clas...

Yeah - we have something very similar to that and the issue is that modern responsive grid systems allow you to do things like reorder columns at different breakpoints or change the size of columns at breakpoints, ect... Our design folks are asking for a level of flexibility we need to find a way to...

Arun - yes; you can change the tag name, but I'm looking to change the name of the classes. Also - as I understand it, if you ​remove the tag, then the component becomes un-editable.

The problem with that is that if we hide the wrapper completely; then the dialog doesn't work :/Also - I've tried `.getOptions(getRequest(), true).getCssClassNames().add("TEST_CELL");` for IncludeOptions and it doesn't seem to work.