[Users] [Bug 3543] New: recent message causes mimeview to open html from a previously viewed html message

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Tue Oct 20 01:27:36 CEST 2015


            Bug ID: 3543
           Summary: recent message causes mimeview to open html from a
                    previously viewed html message
    Classification: Unclassified
           Product: Claws Mail
           Version: GIT
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: UI/Message View
          Assignee: users at lists.claws-mail.org
          Reporter: pf at pfortin.com

See list archive:

Not sure what the trigger is yet; but I moved the message into a fresh CM
instance and cm --debug reports this when I try to view the html via Fancy:
Vector smash protection is enabled.
fancy_viewer.c:83:fancy_get_widget: 0x1b06930
fancy_viewer.c:83:fancy_get_widget: 0x1b06930
fancy_viewer.c:249:using UTF-8 charset
fancy_viewer.c:252:zoom_level: 100
fancy_viewer.c:385:navigation requested to
openjdk version "1.8.0_60"
OpenJDK Runtime Environment (build 1.8.0_60-b27)
OpenJDK 64-Bit Server VM (build 25.60-b23, mixed mode)
fancy_viewer.c:444:Starting request of 58

There seems to be a corner case where the current message number is not updated
before calling mimeview.  In fact, I can view any message in any folder and:
1) if the last viewed message has html, last message's html is what I see; or, 
2) if the last viewed message has no html, I get a blank text area.

So far, things I've found wrong with the trigger message are:
- a mismatched double-quote -- removing it doesn't change anything obvious.
- missing href="..." on 4th anchor -- adding it doesn't help
- missing html code, such as:
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.=
  <html xmlns=3D"http://www.w3.org/1999/xhtml">

Adding the above html code allowed Fancy to display the html portion.

While this is a sender error; the CM bug is in not at least initializing the
message pointer to avoid displaying some other message's content.

You are receiving this mail because:
You are the assignee for the bug.

More information about the Users mailing list