Closed
Bug 193
Opened 26 years ago
Closed 26 years ago
Non-Latin-1 strings in frameListmenu are not displayed properly
Categories
(MozillaClassic Graveyard :: XFE, defect, P2)
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: jshin, Assigned: ramiro)
Details
Created by Jungshik Shin (jshin@pantheon.yale.edu) on Monday, April 13, 1998 4:19:32 PM PDT Additional Details : Open multiple browser windows and make each of them display web pages with non-Latin-1 strings as their titles. FrameList menu display titles of those pages in Compound text encoding. This is always the case in Communicator/Navigator up to 4.05. In Mozilla (19980331), it''s not consistently the case. For some pages, Frame List menu displays the title correctly while for other pages, Frame List menu displays the title in Compound text encoding. ns/cmd/xfe/src/FrameListmenu.cpp gets the title of the frame using XFE_Frame->getTitle().(defined in Frame.cpp). The way it returns the title of the frame is inconsistent. Sometimes, it returns it in locale-dependent encoding and othertimes it returns it in Compound Text encoding of Xlib. In the former case, a subsequent call to convert locale-dependent encoding to Compound String of Motif leads to the correct result while in the latter case, it doesn''t. Updated by Ramiro Estrugo (ramiro@netscape.com) on Friday, April 24, 1998 9:29:47 PM PDT Additional Details : Assigned to ramiro@netscape.com I think we can fix this by not using XFE_Frame::getTitle() which as you indicate seems to be flaky. Instead we can store the title when the back end calls XFE_SetDocTitle() and used that stored string in the frame. So that when XFE_FrameListMenu iterates through the frames, it gets what the backend thinks should be the right thing for the title. This we know will work, since titles for documents are not broken in the BE as far as we can tell.
Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•