Having spent most of the day on this issue. I can really only tell you that Safari decided to handle iframe events differently then all the other browsers. This is also different to other versions of Safari which does work as intended. There is nothing in their changelog related to this. I’m either going to retool drag and drop to support this or submit a ticket to Apple about this. In either case it’s not going to be a quick fix. We’re going to move on for now and report this in our tracker. I recommend not using safari if you are looking to use the drag and drop feature of the Element Library.
Thanks @charlie – that’s one issue I reported. The other is about Components not showing up after being created, or not having changes applied without re-saving the pages where they occur. Other people are corroborating – can you please take a look at that?
Thanks,
Cheshire
1 Like
The common thing for components not showing up is usually from creating a component from a Cell or a Column. If you create a component from that you would need to CTRL or MOD + Click on the plus button when inside a Grid for the cells and Row for a column component. When you reload Cornerstone does it show up?
For component changes not occurring. Are these parameters that are not changing? If so you probably need to setup an initial value for the parameter and change that to change all subsequent usages of the Component. Is this using a slot? If so that is something that won’t change from a component being saved, but will show changes when you delete the component and re-add it. Does the issue persist if you reload Cornerstone instead of re-saving?
I won’t be able to take a look at the site till Thursday, but if you think I’m off please send another login link this one has expired.
Same problem here on + 25 sites with Pro / X.
Problem started with Safari 17.3. Most recent is 17.4 and no change.
I would really love a fix!
Hi @charlie – no, the components were made from button and text elements, not columns or grid cells.
In the case of the updated component not refreshing where it’s assigned without resaving page where it’s assigned, you can see it in the “home button” component. I’ve extended the temp login, added here again. When you go to Cornerstone and look at the Home Button component, you’ll see that the button is a different color than the home page, which is where the component is used. The button color is NOT a parameter to be changed – the button color is only meant to be defined in the component file itself.
Hope you can decipher this…
The color is fine when I visit your site. The color should be black right? Can you send us a screenshot of what you see? I’d possibly try to clear your browser cache to and see if that fixes the issue.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.