fregante / GhostText

👻 Use your text editor to write in your browser. Everything you type in the editor will be instantly updated in the browser (and vice versa).
https://GhostText.fregante.com
MIT License
3.25k stars 116 forks source link

ghosttext is unresponsive in chrome when clicking on extension icon or using keyboard shortcut #230

Closed superjase closed 1 year ago

superjase commented 1 year ago

Setup

i am not sure where to post this, as i couldn't find another forum. Browser: chrome version 103.0.5060.134 (official build) (64-bit) (latest) Editor: sublime text stable channel build 4126

Description

ghosttext was working perfectly in chrome yesterday. i have not installed any chrome extensions or ST packages since then.

i have just updated chrome with no success.

i have tried disabling all other extrensions.

it is no longer working in chrome, but works in firefox. the ports are identical (4001) for chrome and firefox. ST is clearly working properly on its side, as the text loks in ST the extension is used in firefox.

in chrome: when i click on the ghosttext extension icon, nothing happens. previously, text boxes would highlight with a green border and clicking on the required textbox would highlight that box in blue, and sublime would reflect the html. now nothing happens at all. no green highlight. no visible response. no code in sublime. it's like clicking on a piece of text - click, and nothing.

i do not receive an error message. my other extensions are working perfectly (eg stylus, window resizer, reddit enhanceent suite).

i have: uninstalled the GT extension in chrome and reinstalled. uninstalled the GT packege in ST and reinstalled (both of these reinsatllations with restarts of chrome and ST). i have reoponed tabs, check on multiple sites (eg our company site, this page, w3schools.com, https://ghosttext.fregante.com/troubleshooting/). i have restarted windows.

ghosttext 01 ghosttext 02 ghosttext 03

fregante commented 1 year ago

Thank you for the report! A new version was just released but chrome hasn’t accepted it yet. Wait for v22.7.20

superjase commented 1 year ago

it's working again now. thanks for the quick turnaround :)

fregante commented 1 year ago

Done, 22.7.20 is available everywhere