How to change the default transition duration in Cornerstone?

[Jloupf]

Hi,
I’m trying to figure out whether it’s possible to change the default transition duration applied to elements in Cornerstone.

Right now, every element comes with a default transition duration of 300ms, and I would like this value to be 0ms by default. I know I can change it manually for each element in the inspector, but I haven’t found any global setting or configuration option to adjust this default value.

Is there a way (UI option, filter, custom code, or advanced setting) to override the default 300ms transition duration so that every new element starts with 0ms?

Thanks in advance for your help.

[ruenel]

Hello @Jloupf,

Thanks for writing in! By default, in the stack styles, there is this built-in CSS:

 .x-td, .x-div, .x-row, .x-col, .x-grid, .x-cell, .x-section, .x-acc-header, .x-acc-header-indicator, 
.x-crumbs-link, .x-paginate-inner>*, .x-anchor, .x-anchor-text-primary, .x-anchor-text-secondary, 
.x-anchor-sub-indicator, .x-anchor.has-int-content .x-anchor-content, .x-bar-is-sticky, 
.x-bar-is-sticky .x-bar-content, [data-x-toggle-collapse], .x-graphic-child, .x-image, .x-line, 
.x-mini-cart li, .x-mini-cart a:not(.x-anchor), .x-modal-close, .x-search, .x-search-btn, 
.x-search-input, .x-icon, .x-text, .x-text-content-text-primary, .x-text-content-text-subheadline, 
.x-text-typing, .x-typed-cursor, .x-menu-first-level, .x-menu-layered:not(.x-menu-first-level), 
.x-wc-add-to-cart-form, .x-wc-shop-sort, [data-x-particle], .x-bar, .x-bar-scroll-button, 
.x-bar-container, .x-slide, .x-slide-pagination, .x-slide-pagination li
Specificity: (0,1,0)
 {
    transition-duration: .3s;
}

You can override the transition duration by modifying the code above and add it to your Theme Options GLobal CSS or in your child theme’s style.css file.

Hope this helps.

[Jloupf]

Thanks for your help.
I applied the CSS override and it works as expected: the transition duration on the front end is now 0 ms.
In the builder, the default value still shows 300 ms, but the actual behavior on the live site is correct, so this solution works for my needs.

Thanks again for the support!

[tristup]

Hi @Jloupf,

Glad that we are able to help you.

Thanks