Feature request: lock css/theme prefereces when 2 tabs or more are open

Hello,
I don’t know if it’s possible or if it’s already happened to someone else, but sometimes the following happens to me:

I have e.g. 2 tabs open, because I for example check something in tab 1 for a layout and then implement it in tab 2.
then it happens that i have changed css code or theme settings in tab 1 and saved them. now i change css code or theme settings in tab 2 and save. now of course all the things that were saved in tab 1 are gone again or overwritten.

would it be possible to somehow implement a “lock” function here? or some other solution so that css/theme settings can only be changed in one tab?

thanks in advance!
best regards
harry

1 Like

Yes! Have noticed this a fair bit, anything global I imagine, not just CSS as it’ll keep the state on whichever is the latest that you save.
But definitely have had it before when styling disappears because of this scenario.
Maybe not a ‘lock’ as you may not know/forgotten that you have another tab open or you may not even be in the CSS for another tab, just working on multiple pages/layouts.

That also happend do me.

I start with only one backend-tab and only one frontend-tab, to avoid overwriting things. But then, I use the frontend to check other pages and then choose “edit in cornerstone” on the new page - now to editors are open and I have to be very carefull not to overwrite the other tab.

So If there would be a solution for that - a lock, or a warning like “this page / setting has been saved from another tab” would be great.

Best regards

Uli

1 Like

It happened to me as well. :slight_smile: I have managed to save the day a few times due to the fact that undo is active on the page as long as it is opened, even after saving changes.

Hey @deranaloge,

I apologize for not chiming in sooner. Unfortunately, this one isn’t very actionable at the moment. Like @RubberDuckers mentioned, it does effect any changed state. This could be Theme Options, global CSS, preferences, colors, fonts, etc.

The best way to solve this is synchronizing that state between browser tabs. This would take quite a bit of refactoring to allow our app to support it unfortunately.

1 Like