[Pidgin] #8819: Pidgin will "auto-raise" window on XMPP messages

Mon Mar 30 13:02:20 EDT 2009

#8819: Pidgin will "auto-raise" window on XMPP messages
--------------------------------------+-------------------------------------
 Reporter:  Lobsang                   |           Owner:  lschiere    
     Type:  defect                    |          Status:  pending     
Milestone:                            |       Component:  unclassified
  Version:  2.5.5                     |      Resolution:              
 Keywords:  xmpp, raise conversation  |   Launchpad_bug:              
--------------------------------------+-------------------------------------
Changes (by deryni):

  * status:  new => pending

Old description:

> After upgrading to 2.5.5, messages received from other users using
> libpurple (pidgin, adium, etc) will cause the conversation window to open
> (and raise) even though pidgin is set to not do so.
>
> Initially, I thought this could be related to the OTR plugin, but the
> problem happens even after I disabled all plugins and restarted pidgin.
>
> Here's a sample XMPP message that causes it (formatting added for ease of
> viewing):
>
> (This is the user beginning to type. At this point, everything is normal
> and the window is not improperly raised)
>
> <message type='chat' id='purplea7829a0d'
>          to='foo at bar.com/TritonA401F236'
>          from='moo at cow.com/AdiumEC1CEF28'>
>   <composing xmlns='http://jabber.org/protocol/chatstates'/>
>   <x xmlns='google:nosave' value='disabled'/>
>   <record xmlns='http://jabber.org/protocol/archive'
>    otr='false'/>
> </message>
>
> (This is when the problem happens)
>
> <message type='chat' id='purplea7829a0e'
>          to='foo at bar.com/TritonA401F236'
>          from='moo at cow.com/AdiumEC1CEF28'>
>   <active xmlns='http://jabber.org/protocol/chatstates'/>
>   <body>This is a test message</body>
>   <html xmlns='http://jabber.org/protocol/xhtml-im'>
>   <body xmlns='http://www.w3.org/1999/xhtml'>
>     This is a test message</body>
>   </html>
>   <x xmlns='google:nosave' value='disabled'/>
>   <record xmlns='http://jabber.org/protocol/archive' otr='false'/>
> </message>
>
> I'm no expert in XMPP, but is it normal to have the message being sent
> twice, once in "plain-text" and again inside an HTML container?
>
> I tried the same using the Google web talk client and the problem does
> not happen.
>
> -- Lob

New description:

 After upgrading to 2.5.5, messages received from other users using
 libpurple (pidgin, adium, etc) will cause the conversation window to open
 (and raise) even though pidgin is set to not do so.

 Initially, I thought this could be related to the OTR plugin, but the
 problem happens even after I disabled all plugins and restarted pidgin.

 Here's a sample XMPP message that causes it (formatting added for ease of
 viewing):

 (This is the user beginning to type. At this point, everything is normal
 and the window is not improperly raised)

 {{{
 <message type='chat' id='purplea7829a0d'
          to='foo at bar.com/TritonA401F236'
          from='moo at cow.com/AdiumEC1CEF28'>
   <composing xmlns='http://jabber.org/protocol/chatstates'/>
   <x xmlns='google:nosave' value='disabled'/>
   <record xmlns='http://jabber.org/protocol/archive'
    otr='false'/>
 </message>
 }}}

 (This is when the problem happens)

 {{{
 <message type='chat' id='purplea7829a0e'
          to='foo at bar.com/TritonA401F236'
          from='moo at cow.com/AdiumEC1CEF28'>
   <active xmlns='http://jabber.org/protocol/chatstates'/>
   <body>This is a test message</body>
   <html xmlns='http://jabber.org/protocol/xhtml-im'>
   <body xmlns='http://www.w3.org/1999/xhtml'>
     This is a test message</body>
   </html>
   <x xmlns='google:nosave' value='disabled'/>
   <record xmlns='http://jabber.org/protocol/archive' otr='false'/>
 </message>
 }}}

 I'm no expert in XMPP, but is it normal to have the message being sent
 twice, once in "plain-text" and again inside an HTML container?

 I tried the same using the Google web talk client and the problem does not
 happen.

 -- Lob

--

Comment:

 Yes, it is normal to have both plain and xhtml-im message blocks, though
 applications are supposed to only send the xhtml-im block when there is
 formatting involved, which pidgin doesn't currently do.

 Does this happen for all messages from all buddies? Does it only happen on
 certain protocols? Does it only happen for certain buddies? Do you have
 the message notification plugin loaded? If so, what options do you have
 enabled in it?

 Can you get the message stanza from the Google Talk web client that
 doesn't trigger this issue?

 Does this issue go away if you disable custom smileys for your XMPP
 account? That option is in the Modify Account dialog.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/8819#comment:1>
Pidgin <http://pidgin.im>
Pidgin