77348 - Sidebar: International country folders need localized titles

Status: RESOLVED INVALID

(SeaMonkey :: Sidebar, defect)

Description

[Lynn Webb]

If I go to the sidebar customization window and open the International folder, I 
see the countries listed in English, since I'm on a US operating system. Then, 
the country names change to their native language when I click on them, which is 
correct functionality. The problem comes up during the same session when I close 
the International folder and reopen it. At this point, I can no longer view the 
countries in their native language, even if I click on the country folder. I 
will attach screenshots describing this problem (see allpanels.jpg and 
allpanels2.jpg).

This problem comes up because two titles get defined for the folders. First the 
US titles are given in international.rdf. Then the localized names are given in 
base-panels.rdf for the different locals. When the second file loads you end up
seeing the new title. However, the sneaking thing about rdf is that the second 
title does not overwrite the first. The second title gets added in addition to 
the first title. When the panel is closed and reopened, the tree code picks up
the first title again. The title of the folder cannot be reliably changed by 
base-panels.rdf. Either always show the localized title, or always show the US 
version.

Comment 1

[Lynn Webb]

------ Additional Comments From [e-mail] 2000-08-24 11:43 -------

Nav triage team: This seems like an edge case. It's inconvenient, but no loss of 
data. nsbeta3-



------- Additional Comments From Lynn Webb 2000-09-25 15:26 -------

Don't know who to assign to now that Steve is gone. Please assign to the 
appropriate person. Thanks.



------- Additional Comments From [e-mail] 2000-09-26 14:25 -------

back to don to hold whilst he figures such things out.



------- Additional Comments From Viswanath Ramachandran 2000-12-06 11:31 -------


Since Don has left, Vishy is taking his bugs in bulk, pending reassignment.
thanks,
        Vishy



------- Additional Comments From Paul Chen 2001-01-26 15:14 -------

nav triage team:

Marking nsbeta1+



------- Additional Comments From shrirang khanzode 2001-01-31 20:27 -------

spam : changing qa to sujay (New Sidebar QA)



------- Additional Comments From [e-mail] 2001-02-19 12:56 -------

over to matt.



------- Additional Comments From Paul Chen 2001-03-09 12:51 -------

Moving nsbeta1+ from status whiteboard to keyword

------- Additional Comments From Viswanath Ramachandran 2001-04-20 00:29 -------

as discussed in team meeting, moving all Nav+ team members nsbeta1+ P3 bugs from 
mozilla0.9.1 to mozilla0.9.2. 

Comment 2

[Lynn Webb]

Attachment: Country folder showing localized title

Comment 3

[Lynn Webb]

Attachment: Country folder going back to English title

Comment 4

[timeless]

i think i filed this bug in the 40xxx's. Nope I'm wrong. Feel free to reopen 
that bug :)

*** This bug has been marked as a duplicate of 38543 ***

Comment 5

[Lynn Webb]

This was newly created based on an older bug related to commercial builds.

Comment 6

[Linda Baliman]

Adding intl keyword

Comment 7

[Paul Chen]

nav triage team:

Lynn, can you reproduce this on a localized build on a localized OS?

Marking target milestone mozilla0.9.2 and p3

Comment 8

[Lynn Webb]

Yes, but the difference is, for example, that if I am using a German build on a 
German OS, I will see all other countries in German instead of English and then 
once I click on the individual country folder it changes to the language of that 
country. I think it would be better either to make the individual country 
folders always display the native language of the country folder or they should 
never display the native language of the country folder. Mixing two languages is 
not a good user experience.

Comment 9

[Viswanath Ramachandran]

Jaime - can you weigh in on what the priority of this shd be for mozilla0.9.2? 

Comment 10

[Jaime Rodriguez, Jr.]

Vishy - I'd keep it in M0.9.2, but leave it as P3. Thanks.

Comment 11

[matt]

i imagine this might be a cache problem.   We should look into this.  Maybe the 
server can expire the ref page immediately so we pull it again from the server.   
Needs investigation
havent' looked at

Comment 12

[Viswanath Ramachandran]

sidebar+pdt triage: we shd just choose if we want the locallized titles or the 
build language titles and stick to that rather than the behaviour where it 
changes the first time you click on it. in any case, this is a nice to have so 
moving to m0.9.3. 

Comment 13

[Paul Chen]

nav triage team:

Moving out to mozilla0.9.4

Comment 14

[Paul Chen]

nav triage team:

Not a mozilla0.9.4 stopper, pushing out to mozilla0.9.5

Comment 15

[Asa Dotzler [:asa]]

0.9.5 is out the door. bumping TM up by one.

Comment 16

[Samir Gehani]

Taking.

Comment 17

[Jay Farrell]

Just wanted to mention that I saw this issue on the OpenVMS build from 20020114

Comment 18

[Samir Gehani]

Sidebar triage team: -> Future

Comment 19

[Jay Farrell]

After seeing the countries names change to their native language, if I close 
the International folder and reopen it, I still see the files in their native 
langueage. I think this means this bug is no longer a problem.
I'm testing on V1.0 RC2, openvms build 20020513

Comment 20

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 21

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 22

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 23

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 24

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 25

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 26

[Karsten Düsterloh]

This part of Sidebar customization is long gone.