Closed
Bug 87535
Opened 25 years ago
Closed 25 years ago
View -> Languages and Web Content -> Download More should not bring up restart mozilla dialouge
Categories
(Core :: Internationalization, defect)
Core
Internationalization
Tracking
()
VERIFIED
FIXED
mozilla0.9.3
People
(Reporter: hendikins, Assigned: jbetak)
References
Details
(Keywords: regression, Whiteboard: nsbranch+,pdt+)
Attachments
(2 files)
|
1.42 KB,
patch
|
Details | Diff | Splinter Review | |
|
1.47 KB,
patch
|
Details | Diff | Splinter Review |
Reproduction shouldn't be a problem. Since this option brings up a webpage
instead of changing settings, the dialouge shouldn't appear.
Comment 1•25 years ago
|
||
I suspect that this is intended, but it can be considered annoying.
Status: UNCONFIRMED → NEW
Component: Browser-General → Internationalization
Ever confirmed: true
Comment 5•25 years ago
|
||
Is this a regression? Does NS6.1 PR1 have this problem?
Comment 7•25 years ago
|
||
Reassigning to bobj for now. cc'ing Roberets to watch this one, while I am on
vacation.
Bob - Can you take a look at this?
Assignee: tao → bobj
Comment 10•25 years ago
|
||
The following code checkes the two locale values (old and new) then alerts if
they are different.
http://lxr.mozilla.org/seamonkey/source/xpfe/components/prefwindow/resources/content/pref-appearance.xul#52
In case of "Download More", it could be treated as unmatched case.
Juraj, is that your code or added by ben?
Comment 11•25 years ago
|
||
Juraj, I looked at bug 65251 and switchUILanguage is your code, so reassign to
you.
I don't see "general.useragent.locale" is modified by the UI language switch so
the comparison always done against the original language not the current one.
I think "general.useragent.locale" should not be modified by UI language switch.
If the current UI language has to be remembered then probably need a separate
pref.
Assignee: nhotta → jbetak
Comment 12•25 years ago
|
||
The code I mentioned was for pref dialog, so probably not causing the menu
problem. I just talked to Juraj about that, he is going to look at this bug
anyway, thanks.
| Assignee | ||
Comment 13•25 years ago
|
||
Naoki,
so I had a look and it seems that Ben somehow omitted
"chromeRegistry.selectLocale(langcode, true);" from the original patch when
changing from alert() to promptService. This is significant in two ways:
1) without this statement the menu items cannot be used to set UI or content
locale.
2)When the language code is empty, as when the "Download More" item was
clicked, chromeRegistry.selectLocale fails and we don't display the alert
message. So without it we are getting the bogus alert.
Please see the attached patch, which also addresses the somewhat lame concept
for bypassing the alert, when language code == null. Since this affects the
branch, should we add nsBranch and try to get approval to check it in?
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.3
| Assignee | ||
Comment 14•25 years ago
|
||
Comment 15•25 years ago
|
||
r=nhotta
| Assignee | ||
Comment 16•25 years ago
|
||
cc'ing alecf for potential sr
Comment 17•25 years ago
|
||
sr=alecf
for future reference, this code is kinda useless:
var chromeRegistry =
Components.classes["@mozilla.org/chrome/chrome-registry;1"].getService();
if ( chromeRegistry ) {
chromeRegistry = chromeRegistry.QueryInterface(
Components.interfaces.nsIChromeRegistry );
}
namely because getService() will throw an exception if the service is not found
- basically chromeRegistry will always have a value... if you are not sure if
the service will be there (i.e. that getService() will fail) then you should
wrap this with try/catch
but that code isn't actually part of THIS patch so it doesn't change the review
status
| Assignee | ||
Comment 18•25 years ago
|
||
| Assignee | ||
Comment 19•25 years ago
|
||
alecf,
thanks for pointing this out - I'd suggest addressing it now. What's strictly
required for this bug amounts to a 1-line change, and the larger part of the
patch is already devoted to clean-up...
Comment 20•25 years ago
|
||
sr=alecf on that too
| Assignee | ||
Updated•25 years ago
|
Whiteboard: waiting for 0.9.2 a=
Target Milestone: mozilla0.9.3 → mozilla0.9.2
Comment 21•25 years ago
|
||
please check into trunk and keep this bug open for moz0.9.2 landing.
Whiteboard: waiting for 0.9.2 a= → r=nhotta, sr=alecf waiting for 0.9.2 a=
Comment 22•25 years ago
|
||
pushing out. 0.9.2 is done. (querying for this string will get you the list of
the 0.9.2 bugs I moved to 0.9.3)
Target Milestone: mozilla0.9.2 → mozilla0.9.3
| Assignee | ||
Comment 23•25 years ago
|
||
Asa,
I apologize for marking this 0.9.2. We are merely interested in obtaining
branch checkin approval, as this addresses key i18n/l10n functionality and
fixes a menu item regression.
Whiteboard: r=nhotta, sr=alecf waiting for 0.9.2 a= → r=nhotta, sr=alecf, waiting for branch checkin a= (requested on 06/28/01)
Comment 24•25 years ago
|
||
jbatek. Actually it should have been me apologizing for the trespass. The
Target Milestone traditionally belongs to the bug's Assignee (in this case, you)
and I generally don't mess with it except that it was targeted at a Milestone
that is now passed. If you are still trying to get this landed on the branch I
believe that you need to email pdt2@netscape.com.
| Assignee | ||
Comment 25•25 years ago
|
||
Asa,
thanks for clarifying this - I just emailed PDT...
Whiteboard: r=nhotta, sr=alecf, waiting for branch checkin a= (requested on 06/28/01) → r=nhotta, sr=alecf, waiting for branch checkin pdt approval (requested on 06/29/01)
| Assignee | ||
Updated•25 years ago
|
Whiteboard: r=nhotta, sr=alecf, waiting for branch checkin pdt approval (requested on 06/29/01) → r=nhotta, sr=alecf, trunk fix checked in, waiting for branch checkin pdt approval (requested on 06/29/01)
| Assignee | ||
Comment 26•25 years ago
|
||
waiting for the plan for lifting trunk fixes to the branch to materialize, will
take additional steps after that...
Comment 28•25 years ago
|
||
This was landed to trunk at Jun 29 15:00
Comment 29•25 years ago
|
||
Changing Platform and OS to All as I reproduced the original problem on WinMe-Ja
and MacOS9.1 (using 07-03-03-0.9.2). About to verify fix on latest trunk build...
OS: Linux → All
Hardware: PC → All
Comment 30•25 years ago
|
||
Verified on trunk on Win32, Linux, and Mac as follows:
07-03-11-trunk on WinMe-Ja
07-03-10-trunk on MacOS-9.1
07-03-18-trunk on Linux Redhat 7.1-Ja
Need to verify on branch when fix checked in there.
Whiteboard: r=nhotta, sr=alecf, trunk fix checked in, waiting for branch checkin pdt approval (requested on 06/29/01) → r=nhotta, sr=alecf, trunk fix checked in, waiting for branch checkin pdt approval (requested on 06/29/01), verified on trunk
Comment 31•25 years ago
|
||
mark it as nsbranch+
Whiteboard: r=nhotta, sr=alecf, trunk fix checked in, waiting for branch checkin pdt approval (requested on 06/29/01), verified on trunk → nsbranch+
Comment 33•25 years ago
|
||
land 92 branch. mark it fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 34•25 years ago
|
||
fixed and check into m92
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 35•25 years ago
|
||
fix in m92
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 36•25 years ago
|
||
Verified on branch on Win32, Linux, and Mac as follows:
07-10-05-branch on WinMe-Ja
07-13-03-branch on MacOS-9.1
07-13-04-branch on Linux Redhat 7.1-Ja
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•