Search code examples
google-chromegoogle-chrome-devtoolsmacos-monterey

Copy text in chrome DevTools/Console panel not work normally

Describe the bug

Recently, while using Chrome (version 112.0.5615.49) on macOS (version 12.6.3), I have encountered an issue when copying and pasting from the Console panel in DevTools. After selecting a word and copying it, when I paste it, it always shifts 2 characters backwards. What could be the reason for this?

To Reproduce

Steps to reproduce the behavior:

  1. Any page, F12 to open devtools, switch to console panel
  2. Select and focus on a word(for example: the word 'Uncaught' in sentence Uncaught ReferenceError:), do cmd + c or right click & select copy on this word.
  3. cmd + v or right click & select paste anywhere, you get error word, caught R

Expected behavior

Copy 'Uncaught', paste will print 'Uncaught'

Screenshots

screen recording gif

same screen recording video

Desktop

  • OS: macOS (12.6.3 (21G419))
  • Browser [Chrome]
  • Version [112.0.5615.49]

So, is it a chrome bug? or waiting for offical upgrade to fix it?

Solution

  • 20230504: Today I upgrade to 113.0.5672.63(macOS), all goes well now. Below are my personal little notes.

    Finnaly it fixed with new version 112.0.5615.121. What a horriable days.

    Now it surely chrome bug, not my mac's problem.

    Everyone should upgrade chrome to avoid it.

    ===20230417===

    It broken again. I send a feedback report to chrome, but no reply yet.

    ===20230419===

    I check new upgrade everyday. Now is 112.0.5615.137, still bad ;(

    ===20230504===

    More and more people could reproduce(macOS/Windows/Ubuntu), I think all of v112.x chrome in this post mentioned work bad.

    Saddly, I still not received any email about that I seed the feedback 20 days defore, and I don't know how to trace the progress. Any bro knows how to submit the feedback to chrome to be fix more efficient.

    I seem to have gotten used to this headache-inducing bug and will quietly wait for the official fix(laughing cry :)

    After I ready post my hopeless words. I suddenly realized that I hadn't actively checked for updates in a long time, and just now I found that there was an update available when I opened 'About Google Chrome'. I updated to version 113.0.5672.63 (macOS), and after restarting Chrome, it seems that the issue has finally been fixed. That's great news!

    Please check your chrome update, I think v113.x fixed it, but I'm not sure if the update has been released for other operating systems yet, check yourself guys.