Drag-and-Drop Broken in GoHighLevel Website/Email Builders after v1.85.116 Update (Mac M4)

Browser Support Desktop Support
,
1

Hello,

I am experiencing a persistent issue where the drag-and-drop functionality is completely disabled in the GoHighLevel (GHL) website and email builders. This started immediately after the latest Brave update (v1.85.116, Chromium 143).

System Specs:

  • Device: MacBook Air M4

  • OS: macOS Sequoia (latest)

  • Brave Version: 1.85.116

The Problem: Elements in the GHL builder can be selected, but cannot be moved. The “grab” action does not initiate. This works perfectly in Safari, but is broken in Brave (even in Private Mode with all Extensions/Shields disabled).

Troubleshooting already performed:

  • Disabled Brave Shields and Hardware Acceleration.

  • Tried Private/Incognito mode.

  • Reset all brave://flags and specifically toggled “Touch UI Layout” and “Smooth Scrolling.”

  • Launched via Terminal using --disable-touch-events.

  • Re-installed Brave and cleared site-specific cookies/data.

Since this was working prior to the December update, it appears to be a regression in how Chromium 143 handles pointer events or drag-and-drop APIs on Apple Silicon.

Is there a known fix or a specific flag I can toggle to restore legacy drag-and-drop behavior?

Thanks.

2

Can you quickly try downloading the Beta and testing this behavior in the Beta to see if it has the same issue?

Additionally, can you please try testing this in another Chromium based browser (Chrome, Edge, Opera, etc.)? If the issue is indeed Chromium specific this should confirm that.

3

Hi Mattches,

I tested the Brave Beta app, and the drag-and-drop feature is working there. And it’s working on the Chrome browser as well. Only it doesn’t work on the normal Brave app. How can I resolve this issue?

4

If it’s working in the Beta than either the issue is still somehow profile specific (although unclear how that would be the case given that you tested after reinstalling/clearing site data) or whatever was causing the issue is resolved in the updates that Beta has and will be inherited by the stable browser once it updates to that build.

We can perform one more test to see if it’s profile specific by creating an additional browser profile and testing the behavior there:

  1. In Brave (stable) open the main menu, go to More tools --> Add profile
  2. Create a new profile, when close your original profile window (only the new profile window should be open)
  3. Visit the site and try to reproduce the error
5

I also did this, and the same issue persists.

6

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