Color Diff text briefly appears then is reverted back to original

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Using thunderbird 15.0 on Ubuntu
2.  Open a git repo commit email
3.

What is the expected behavior? What do you see instead?
I expect to see the colored diff.

What I see is the colored diff briefly appears for about 0.5 seconds.  Then it 
is replaced with the original email plain text.  It is as if something in tb is 
overwriting what the plugin is doing.

What version of the product are you using? On what operating system?
tb version 15.0
ubuntu 12.04.1
plugin ver 0.6.2011.11.22.17.42.09

Please provide any additional information below.

Please note I followed a suggestion to bump up the maxVersion number in 
install.rdf in order to get the plugin to install.  That's the only change I 
made to the plugin.  Hope that does void my warranty :)

Please also attach a broken mail as an eml file to this bug. It will really
help me to fix it faster.

email attached

Original issue reported on code.google.com by c...@cbrune.com on 9 Sep 2012 at 3:58

Attachments:

• colordiff_example.eml

[GoogleCodeExporter]

When I reported the issue I was using thunderbird inside a VNC session.

When I use thunderbird natively w/o VNC it works great.

The problem could be something with my VNC config.

Please close this issue.

Original comment by c...@cbrune.com on 10 Sep 2012 at 2:47

[GoogleCodeExporter]

Check that, there is something wrong.

An email with an inline git diff is not rendered correctly.  As described above 
it briefly shows up rendered, but quickly reverts to plain text.  The attached 
email above is such a case.

However, patches that are included as "attachments" are rendered correctly.

Possibly a duplicate of issue #68.

Original comment by c...@cbrune.com on 10 Sep 2012 at 2:58

[GoogleCodeExporter]

OK, thanks for update.

Original comment by typr...@gmail.com on 10 Sep 2012 at 3:05

• Changed state: Invalid

[GoogleCodeExporter]

Oops, messages crossing paths.

Please beware that there is no one actively fixing this plugin at the moment; I 
have admin access from the original author, but am not very knowledgeable about 
Mozilla plugin mechanics.

Original comment by typr...@gmail.com on 10 Sep 2012 at 3:07

• Changed state: New

[Qeole]

Obsoleted in v2 by c8436ddca5160c736aaf67326ccbaa08ffb01ae5.