iMac Trackpad Chrome problem | Community
Skip to main content

iMac Trackpad Chrome problem

  • March 11, 2022
  • 4 replies
  • 0 views
J
Since a few days, changes have been made to the agent environment of Zendesk.
 
I work with an iMac, OS 12.2.1 in combination with a trackpad
Chrome browser Version 99.0.4844.51 (Official build) (x86_64)
 
In the text field of the ticket, I am experiencing problems from this change. Outside of the text field, I don't experience any problems in other programs either.
 
Complaint
My trackpad no longer responds to double-tapping to, for example, block a text or adjust a shaded word through the spell-check.
 
When I start Zendesk via Safari, everything works as it should.
 
With my MacBook Pro (completely up to date) I experience exactly the same complaints. So it is not related to 1 machine.
 
Can you help me?

    4 replies

    Gustavo18
    • Gustavo18
    • April 15, 2022
    Hi Jan-Willem,

    This is something better to investigate privately.
     
    As you've created a private ticket with us, let's keep the information on that ticket only.

    Best regards,
    Bill35
    • Bill35
    • May 16, 2022

    I also am experiencing the same.  On Chrome browsers, right-clicking a word that is misspelled in Zendesk field does not allow the auto-correct to work.  Yet in Safari - this works no problem.  I'd say this happened just in the last month or two.  Was the issue above resolved as it may also solve this issue as well.  Please advise.

     

    J

    Unfortunately this problem has not been solved.

    At the request of Gustavo Oliveira, I created a ticket via Zendesk Support and several attempts have been made to resolve it.
    Followed all known steps, but unfortunately…….

    I can't help you further.

    If you have found the solution yourself; please share it here :-)

    Dekbi
    • Dekbi
    • June 2, 2022
    Hi Bill,
     
    We've done some checks on similar issues about this and after looking into this further we, unfortunately, would not be able to offer any resolution to this. 
     
    We would recommend contacting the manufacturer or trying a different device. Worth a try but it would be best to contact the manufacturer of the device that you are using to isolate things further.
    Terms & ConditionsCookie settingsAccessibility statement