Build: 2001-10-20-11-0.9.4 Overview: Only on Linux, KDE, Stand Alone msg: Extra character like "<2>" on the title after 'Netscape 6'. Characters are seen as well on the title of 3 pane window - with previous builds. It is not seen on other platforms or types of Linux (GNOME). Steps to reproduce: From the 3 pane window select a message and double-click on it (or press Enter). Actual Results: Unexpected extra characters at the end on the title bar. Expected Results: No garbage on the title - 3 pane or Stand Alone window. My observations for Stand Alone win: 1. It happened for old and newly created profile. 2. IMAP acct. I saw after "Netscape": 6X<2> 3. POP acct. I saw after "Netscape": 6?H, 6<2>, 6<3>. Sometimes it shows correct title without extra char. I exited current build and retrieved 2001-10-17. Here Stand Alone window mostly does not show any extra char in the title. I saw extra characters like 6<2> couple times. But 3-pane window shows sometimes after "Netscape": 60?X, 62>, 6q, 6H, 6pe H, 6e, 6@ Ninaschka checked this on Netscape RTM. The same problem. Additional Information: It seems that Replies and messages with Attachments have more of this trouble. Simple short messages - mostly OK. Can not state it for sure. Not so many statistic.
olga, other than the standalone msg window, have you seen this in an editor window, mail compose window, or even a browser window under KDE? just curious. wacky that this isn't a problem under gnome... cc'ing akkana, in case she has encountered this.
I've just noticed it on Browser title. I see 'Netscape 60' on the page http://home.netscape.com/download/error.html I was going to retrieve this: http://cgi.netscape.com/cgi-bin/pdms_download_path.cgi Again I see it only KDE. I am now on 2001-10-17 branch build. My Inbox - 3 pane window shows now: 'Netscape 67 8' Neither New Msg Compose nor Composer has a title for the message - no trouble with extra char.
Updating multiple bugs. This is a valid UI issue. Would be nice to have it fixed if time allows.
I believe this bug should be resolved as invalid. Quoting from bug 92150: ------- Additional Comment #13 From Ilya Konstantinov 2001-09-24 10:37 ------- Certainly WFM. The bug is in kdecore's netwm implementation assuming UTF8_STRINGs are always null-terminated while the standard dictates otherwise. I fixed that in 2.2.
I remove nsbeta1- keyword - it was for MachV.
Now I add 'nsbeta1' keyword for Buffy. Sorry, it's faster to edit multiple bugs at once than manually go to each and remove minus.
Mail triage team: nsbeta1-
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52pre) Gecko/2008062601 SeaMonkey/2.0a1pre I've never seen this bug, also not on Thunderbird 1.0.x, 1.5.0.x or 2.0.0.x. Is anyone still seeing it? If you do, please tell us in which _recent_ build.
QA Contact: olgam
Yes I see it all the time. It's quite standard behaviour for the window manager to add <2>, or <3> etc. when you open several windows of an application. ->INVALID
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
(In reply to comment #10) > Yes I see it all the time. It's quite standard behaviour for the window manager > to add <2>, or <3> etc. when you open several windows of an application. > > ->INVALID > Yes, I see <2> etc. when several windows would otherwise have the same title (even in different apps, e.g. "Confirm setting cookie" between SeaMonkey & Firefox); but not the strange characters: 6, 6X, 60?X, 6pe H, etc. mentioned in comment #0.
Yeah, that part is definitely WFM for me too:)
You need to log in before you can comment on or make changes to this bug.