Text not returning to textarea with Aquamacs 2.4 about emacs_chrome HOT 9 OPEN

It's likely the web-pages have changed the way they handle text areas. Have you got some specific URLs I can check? Does it still work on other sites? For example can you edit github text areas ok?

from emacs_chrome.

Perhaps I wasn't clear. It's not returning data from the Emacs buffer to ANY sites at all right now... so it's not working at all. Additionally, some of the websites it used to notice (Redmine, the open-source project management and Wiki product) it doesn't even give me the option for anymore.

Regarding github... it recognizes the textarea and puts the blue edit button, but nothing I put in that buffer is returned to the textarea when I close it.

from emacs_chrome.

OK well that's unexpected (and works for me) and also probably a JavaScript issue. If your getting the colour fade then the text has been posted back so it's a DOM update issue.

The first test is to enable Edit with Emacs for Incognito mode and disable all other extensions. If it's still failing can you do Shift-Ctrl-J to open up the console and post the output of the console when you try to do the update?

from emacs_chrome.

Incognito Mode produced the exact same behavior. I used the console log, and below is what I have:

config response: [object Object]
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:280findTextAreas: running over 1
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:319will scan text area in 0
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:321findTextAreas timeout fired
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:280findTextAreas: running over 1
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:319will scan text area in 0
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:332defered 1 updates, next fire in 500
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:321findTextAreas timeout fired
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:280findTextAreas: running over 1
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:319will scan text area in 0
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:321findTextAreas timeout fired
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:280findTextAreas: running over 2
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:319will scan text area in 0
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:332defered 1 updates, next fire in 500
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:332defered 2 updates, next fire in 1000
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:332defered 3 updates, next fire in 1500
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:332defered 4 updates, next fire in 2000
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:321findTextAreas timeout fired
chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:280findTextAreas: running over 1
extensions/event.js:185Error in event handler for 'undefined': TypeError: Object # has no method 'getContent'
at sendTextArea (chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:219:22)
at chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:234:4
at localMessageHandler (chrome-extension://ljobjlafonikaiipfkggjbhkghgicgoh/textareas.js:351:3)
at [object Object].dispatch (extensions/event.js:183:28)
at Object. (extensions/miscellaneous_bindings.js:164:22)

I'm a complete newbie with the console, so I'm not sure if I did everything just right. I had the console running when I started browsing to the page with the textareas, and most of the messages came from that. There were not actually any messages logged when I actually used Edit with Emacs to edit the textarea and return it. The error above came from a click of the extension button in the toolbar, and a green value was returned.

from emacs_chrome.

Interesting. It seems you have discovered a different bug which is that the "edit focused textarea" feature got broken when I re-factored the code. However it doesn't explain the failure your seeing with other types of editing.

Are you confident in running the extension from the development repository?

from emacs_chrome.

I'm not sure what that means Alex... sorry. But I am happy to try
anything... I depend on the extension quite a bit. :-)

On Thu, Mar 22, 2012 at 9:34 AM, Alex Bennee <
[email protected]

wrote:

Interesting. It seems you have discovered a different bug which is that
the "edit focused textarea" feature got broken when I re-factored the code.
However it doesn't explain the failure your seeing with other types of
editing.

Are you confident in running the extension from the development repository?

---

Reply to this email directly or view it on GitHub:
#52 (comment)

from emacs_chrome.

Essentially it's a few simple steps:

git clone git://github.com/stsquad/emacs_chrome.git /path/to/somewhere
disable the Edit with Emacs extension in chrome://settings/extensions
in chrome://settings/extensions select Load Unpacked Repository and point it the cloned repo

from emacs_chrome.

Yes... I have loaded Edit with Emacs as Unpacked. Not sure if you thought
what was in there should fix it though, or if you were just preparing me
for being able to accept modified extensions later. The current code set
does not affect the behavior.

Thanks.

Stewart Bryson
US Managing Director
Rittman Mead
O: 888.631.1410
M: 770.823.7409
F: 888.631.1410
E: [email protected]
[email protected]

On Wed, Mar 28, 2012 at 3:58 AM, Alex Bennee <
[email protected]

wrote:

Essentially it's a few simple steps:

git clone git://github.com/stsquad/emacs_chrome.git /path/to/somewhere
disable the Edit with Emacs extension in chrome://settings/extensions
in chrome://settings/extensions select Load Unpacked Repository and point
it the cloned repo

---

Reply to this email directly or view it on GitHub:
#52 (comment)

from emacs_chrome.

Did you run that with the console open? I would hope at least a few of the errors went away.

from emacs_chrome.