Opened 12 years ago

Closed 12 years ago

Last modified 4 years ago

#1021 closed defect (wontfix)

large messages loose formatting.

Reported by: gnadan Owned by: datallah
Milestone: Component: winpidgin (gtk)
Version: 2.0 Keywords: format message character limit
Cc: seanegan, s-austin1000@…, satya_461

Description

When sending a large text message with formatting ( text and background have color settings, linebreaks, etc ), if the message is over a certain number of characters the message is displayed with no formatting at all. Not sure what the exact character count is that causes this. If I receive the messages using GAIM 1.2.1 all the formatting is there, if I receive the exact same message in PIDGIN, the formatting is gone.

This is on Windows XP

Change History (15)

comment:1 follow-up: Changed 12 years ago by datallah

  • pending changed from 0 to 1

Which protocol are you seeing this with?

comment:2 in reply to: ↑ 1 Changed 12 years ago by gnadan

  • pending changed from 1 to 0

Replying to datallah:

Which protocol are you seeing this with?

Using jabber, so I guess XMPP?

comment:3 follow-up: Changed 12 years ago by datallah

  • Resolution set to wontfix
  • Status changed from new to closed

You're running into a security feature. To prevent performance problems rendering large messages (which could be maliciously exploited to bog down your system), when displaying messages with greater than 100 html tags, the tags are stripped out.

comment:4 in reply to: ↑ 3 Changed 12 years ago by gnadan

Replying to datallah:

You're running into a security feature. To prevent performance problems rendering large messages (which could be maliciously exploited to bog down your system), when displaying messages with greater than 100 html tags, the tags are stripped out.

Very sorry to hear this. We use proprietary jabber clients using Smack, on servers to monitor them, and format the replies using HTML. Sometimes the replies are quite large and that is ok with us. Old versions of GAIM did not have this security feature, right? As I said in GAIM 1.2 - 2.0, it worked ok. It makes Pidgin unusable for me. Would it be possible to make a preference setting that lets you disable this feature or maybe set the limit number? If not able to add to the core preferences, could a plugin be developed to control (turn off or set the limit )this security setting?

I don't want to give up my Pidgin!!!! :-)

comment:5 Changed 12 years ago by rlaager

I don't really know what's going on here, but you *do* have the source.

comment:6 Changed 12 years ago by datallah

  • Cc seanegan added

comment:7 Changed 12 years ago by gnadan

i know, not trying to be lazy... but I am not a developer and thought maybe if it seemed like a worthwhile/reasonable request, somebody who knows what they are doing would take a crack at implementing.

comment:8 Changed 8 years ago by Flow

100 html is unreasonable low. Pidgin should:

  • provide a options to turn on/off this measure and/or provide a setting to increase the number of allowed tags

-at least inform the user, when he receives such a "heavily" tagged messages, that this is happening

comment:9 Changed 8 years ago by deryni

I agree we probably should mention that we have done this. File a new ticket with a feature request asking for that notification message please.

comment:10 Changed 8 years ago by Flow

Done: http://developer.pidgin.im/ticket/13356 And you see no chance that the tag limit will be increased, or even better customizable by the user?

comment:11 Changed 8 years ago by deryni

Certainly not preference-level customizable (it would be possible to support it via gtkrc, or similar, level control).

That being said I don't know that allowing that is all that reasonable. Most people don't hit this limit in the first place. Most that do aren't likely to know what the actual count of tags they got was (or necessarily care to).

Whether the limit could be raised is something that could be discussed but would require (potentially extensive) profiling and testing to come up with another reasonable value.

Not to mention that when the (planned but not short-term) move to webkit occurs this will all be meaningless anyway.

comment:12 Changed 4 years ago by datallah

Ticket #16588 has been marked as a duplicate of this ticket.

comment:13 Changed 4 years ago by satya_461

The ticket I've raised is closed as duplicate of this one. Looks like this is very old ticket(raised 8 years ago).

Is this fixed??

comment:14 Changed 4 years ago by satya_461

Meh, I see this as "Won't Fix" :(

comment:15 Changed 4 years ago by satya_461

An option to configure with default as 100 would have been nice.. :'(

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!