Bug with buttons and break points

Experiencing extremely bizarre behavior in Cornerstone…

See settings here…

Now I change the second breakpoint width to 100%. Which does this…

But here’s the big problem…the page is being viewed at full width (first break point)

What’s going on here?

Hey @co50,

Thanks for writing in! I could not replicate the issue on my end.

Please make sure to set the width of the DIV element wrapper to 100%.

Best Regards.

That doesn’t resemble the page I said the issue was occurring on. It would be impossible for you to try to replicate the layout of the page yourself. That’s why I gave you all the info and login to see it on my end. I didn’t make up the issue. It’s able to be replicated 100% of the time. Setting the container DIV to auto or 100% makes no difference. I need support. This is a serious bug.

-Greg

Hello Greg,

I have logged in to your site and the page isn’t loading on my end.

  • see the secure note below

I have saved the page as a template, downloaded it and imported it to our local testing server. That is where I got the screenshot. My screenshot is using your layout.

Hope this makes sense.

The page loads fine on my end, on every browser. My guess is that Cornerstone starts failing once too many elements are present on a page. We’ve experienced this phenomenon with every large page we’ve ever made in Cornerstone no matter what website and usually the symptoms are just VERY slow previews when you make an edit but this time it seems it’s also messing with breakpoints on at least one element. This is a big problem because it’s prevented us from progressing with the buildout of our page.

Please try another machine or browser - it is very important that the page is loaded exactly as is with all images and code because obviously those are the circumstances that cause Cornerstone to buckle.

I should also note that this is not the result of a plugin conflict - this issue occurs when no plugins except Cornerstone Charts are enabled.

Hello, could I please get some support from someone else? This is holding up our build. Thank you.

Hey @co50,

We will be closing this thread and will respond to your new thread:

Thanks.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.