Closed wang-d closed 11 years ago
Interesting, I was using today without issue. One thing to note is div doesn't look as though it's been tagged by the extension. If you open up the developer tools and turn on the debug output does anything appear there?
I tried again this morning, and it works now. I have changed nothing, but it works now. I guess you should feel free to close this up. Sorry to waste your time.
No worries. The gmail interface has proved to be pretty tricky to support (although much improved since the mutator changes went in). It could be that you were at the wrong end of some of Google's A/B testing that broke Edit with Emacs in some subtle way. If it happens again please re-open the bug.
I type 'c' to open a new compose window. The lower-right corner says "Plain Text". I expect an edit button on the big email-body area, but I don't see it. When I right-click in the big email-body area and choose "Edit in Emacs", the Chrome Console gets a new error "Failed to load resource: the server responded with a status of 400 (Unknown SID) " with the address "https://mail.google.com/mail/u/0/channel/bind?OSID=F553BF25AAD3D0FB&OAID=19&VER=8&at=AF6bupPOHTl3eqRq3BLlogfhOQ6OjdCY7A&RID=rpc&SID=FF732AC8D056B74D&CI=0&AID=20&TYPE=xmlhttp&zx=mrbis0lzikd1&t=1".
I am on chrome Version 27.0.1453.110 and Edit in Emacs 1.12
If I right-click the big email-body area and select "Inspect element", this is the snippet of HTML which Chrome highlights:
I know nothing about web development, so please tell me if I've omitted anything relevant. This behavior is completely deterministic, so I can reproduce it again and get you anything you want.
Any ideas what might be going wrong?