Selecting an element to edit using Cornerstone not working - revisited

Support
#1

Hi,
I write to you regarding my previous post of the same title: Selecting an element to edit using Cornerstone not working.

I am still having the problem.

I have 15 site using X Theme and have a serious problem with this issue. Can you help please as this problem is causing me great pain in time and effort.

I was so impressed with X Theme until this happened, so please please help me to find out why this is happening with an explanation and when the solution for this will be found and implemented…?

I have new site to create and don’t know if I should be using X Theme for them…?

Kind Regards

Roy

#2

I’m also having this problem. Why close the original ticket? Selecting an element to edit using Cornerstone not working

I have updated to X 8.1.1 and Cornerstone 5.1.1 but I’m still having this same issue.

What can we do to solve this problem?

#3

My problem is identical except that if I mouse click a few times on the element and wait patiently, the property of the element eventually opens. If I then do the same on another element, that will eventually open also. This is using my brand new iMac, with all X and WordPress software up to date…

I find that on my old MacBook Pro, all is working as it should. The properties instantly open when selected with the mouse…

This is what is puzzling and why I think support do not want to help as they cannot replicate the issue…
I turned off all plugins, increased php memory to 512, all inactive plugins are deleted…

At this point I am at a loss…?

#4

Hi @RoyPurlan,

Would you mind trying the point releases that we released today? The versions numbers are: X 8.1.2 and Cornerstone 5.1.2. We did fix one performance issue that effected communication between the preview frame and app window. I’m not sure if this is the same problem, but if you could confirm after updating it will help establish a baseline.

I’ve tried to reproduce this in multiple browsers on OS X using a trackpad and external mouse. I’ve also tried on Windows 10. I’ve not been able to trigger the case where inspecting an element is delayed like in your video. I don’t think it’s related to the site (or server) but something client side.

  1. Could you let me know what model mouse you are using? I could look into the possibility of it being device related.
  2. Also, as a quick test could you try clicking the Inspector Breadcrumbs (eg. Section > Row > Column) and let me know how those feel. Do they feel more responsive or about the same? This might help narrow down if the issue is universal to inspecting elements or something related to the preview frame specifically.

@aaron_softwarepromotions, feel free to contribute to the same questions above if you have a moment. Also, a quick aside on your question about the previous thread. All threads are automatically closed by our system after 10 days of inactivity. We’ve found this helpful because there are cases were customers were bumping old threads causing notifications to go to the original poster after the case was handled.

Thanks for your patience as we look into what’s going on here.

#5

Nope. The newer version of X 8.1.2 and Cornerstone 5.1.2. do not solve the problem.

I’m using a Logitech moust M325.

I tested in Chrome and Edge.

#6

I have the same issue, I have to click 25 times on a element to bring up it’s editing pane, it’s very frustrating

#7

Hi Alexander, Many thanks for your reply and help to sort this.

I have made the updates you requested and things are no better.

I am using a new Apple Magic Mouse 2 - rechargeable.

I have been selecting the Inspector Breadcrumbs (eg. Section > Row > Column), and they are working perfectly with instant response.

I also select Outline and select the rows and elements which also work instantly and perfectly.

The problem for me seems to be related to the the preview frame specifically…

There is either a delay or no response in opening the properties of the element when selected in the preview frame…

Looking forward to your reply…

Kind Regards
Roy

#8

Thank you everyone for your patience here. These issues are difficult to investigate because I can’t reproduce any aspect of the presenting issue. Your input here is invaluable to helping us find a solution. It may take us a bit longer to work this out but I’m really hoping we’ll have a solution soon.

@aaron_softwarepromotions, thank you! Your video was helpful to see this in action on another site. I ordered a Logitech M325 and will test with it on my Windows machine when it comes in in a few days. I’m still no sure why or if a specific model would be effected but the closer I can get to the same environment the better, and once I’m able to reproduce the issue I’ll be much closer to fixing it.

@Warlaumont, would you mind sharing your OS, affected browsers and mouse info as well?

@RoyPurlan, thank you! This is very helpful. It’s good to know the problem is specific to the iframe. One of my colleagues has Magic Mouse 2 so I’ll reach out to see if they can help with a bit of testing.

One additional question for everyone: Would you mind trying to use incognito/private browsing and seeing if that makes a difference? I’m curious now if it could be related to an active browser extension.

Thanks again!

#9

Quick update: I was able to get on a call with a colleague who has the Magic Mouse 2 and we confirmed they are having the same issue. I don’t have one of these devices presently but I’m grateful to have more context about what is happening and we are closer to a solution now.

#10

After updating the site that I’m editing locally, it seems that I am also having a similar issue now. I cannot edit anything, the editor is stuck on the spinner after opening it. Tested also in incognito mode (which was a smart suggestion - I also thought it was a plugin) but sadly, I am encountering the same issues.

Screenshot 2021-01-28 at 23.20.35
Screenshot 2021-01-28 at 23.20.351685×1029 60.7 KB

#11

I opened a separate ticket. I think my problem might be different.

Link is below:

#12

I tried everything using Firefox incognito/private browsing only to find it made no difference…

It is good that you are able to replicate the problem with the Magic Mouse 2 and are getting closer to the solution…

Kind Regards
Roy

#13

I cannot edit in Cornerstone using Chrome or Edge. Normal and incognito/InPrivate modes.

I can edit in Cornerstone using Firefox.

#14

Hey @redleome,

Thank you for creating a separate thread for your issue. We will be responding to the thread shortly.

@RoyPurlan, @aaron_softwarepromotions:
I can confirm that this is an ongoing issue with the builder using a Magic Mouse 2. I have done testing using a Trackpad, a generic mouse (wired and bluetooth), and both of these two works perfectly with the builder. With Apple’s Magic Mouse 2, I can hardly click on the elements. This could be because Magic Mouse 2 is using gesture controls. Anyway, @Alexander will be releasing a patch update anytime soon.

Best Regards.

#15

Any news on this issue?

#16

Hi @aaron_softwarepromotions,

I suggest that you upgrade your theme to the latest version because it fixes a lot of issues and then let us know how it goes.

Thank you.

#17

I updated to:
X 8.1.4
Cornerstone 5.1.4

It works! Thank you!

#18

I have also updated and found that it now works much better!

Many many thanks!!

There is one problem though and that is when a Text Panel opens so you can edit the text element, the “x” in the top right corner of the box to close the box, does not work sometimes… it takes 4/5 clicks to close the box…

Kind Regards

Roy

#19

Thanks @aaron_softwarepromotions and @RoyPurlan! Glad to hear it is working for you now.

We ended up discovering it was related to devices that were more sensitive to mouse “move” events. There was a part of the script that cancelled inspect actions if the mouse moved (in case you wanted to start dragging) but some devices seemed to register a move anytime you clicked causing it to fail. I still don’t know if it’s because the mouse actually moved ever so slightly and the sensor picked it up or if synthetically it just dispatches both actions at once.

Roy, I suspect the additional issue you’re seeing is related to a similar event handling scheme. I’ll take a look at this as well. Meanwhile you can press the Esc key to close them consistently, but keep in mind it closes any floating panels you have open.

#20

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