Beta 2: Suddenly I cannot click to any element in Chome to edit it

Hi!

So I have loaded a page with some elements to test something in Chrome. Then I have created a new section and made it two Columns. Then I have double-clicked one of the columns expecting that the Inspector will show the settings for that Column.

However nothing happened. And from that point, nothing happens on any of the pages, even after Clearing the Browser and Server Cache. I cannot edit any element on any page, either by clicking it in the Content view or in the Inspector. All I can do is double-click the text element and edit its text.

No Console errors, no Browser addons active.

Everything is normal in Firefox.

Thanks for the heads up. I’ve tried a few things, but I’ve not been able to make this happen at all. If this is consistently reproducible, would you mind uploading a template of the existing page? Or just sharing logins and page URL in a secure note. Maybe it’s a combination of element settings.

Ok, after few hours, when logging in again, things work again.

Funny. This is a test site and there are few test pages, and none of them were working.

Login details attached.

Thanks!

Thanks! I tried logging in but looks like I’m just a normal user. Could you escalate to an admin? Thanks! I’ll take a look probably sometime tomorrow.

Oh lol, what was I thinking.

Done.
Thanks!

Edit, hmm, something is definitely going on there. Now I’m seeing this:

There is a small JS on the Homepage, but it appears not to be the cause:

let vh = window.innerHeight * 0.01;
document.documentElement.style.setProperty('--vh', `${vh}px`);

and this CSS:

.homehero {
  height:100vh!important;
  height: calc(var(--vh, 1vh) * 100)!important;
}

It’s a same error what i’ve been heading.

Yeah, that looks kinda like this one: https://theme.co/apex/forum/t/cornerstone-refreshing-bug/61718

I just had another thought, so I’m adding a note over there.

1 Like

Yep, dat’s it. “Thing” with unicode.

I tried logging into the site and clicking around (violently :smile: ) but couldn’t get this to reproduce. It feels like a symptom of a deeper issue in the React to HTML system we use in the preview frame but I’ve not been able to confirm anything.

I’ve catched it only once. And it happens on CS refreshes. You can try achieve this effect pushing F5 a hungred of times )

I’ve still not encountered this. If anyone sees it again, let me know about the font family (described on the other thread). Thanks!