Closed
Bug 188100
Opened 23 years ago
Closed 16 years ago
Typo in a phrase could cause some problems with bookmarks schedule
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: atopal, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.3a) Gecko/20021226 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.3a) Gecko/20021226 Phoenix/0.5
I think there is an important typo in the platform neutral jar file
It's in Platform neutral/pippki/mt_default/pippki.properties
The Phrase is called: crlAutoUpdtaeFreqCntError
but I think it should be called: clrAutoUpdtaeFreqCntError
maybe that's why Phoenix would't complain, if I type a figure below 0, in the
schedule for bookmarks.
Can anyone confirm that?
Reproducible: Always
Steps to Reproduce:
1.
2.
Comment 1•23 years ago
|
||
You've spelled both the same way; surely you mean to replace the spelling
clrAutoUpdtaeFreqCntError with
clrAutoUpdateFreqCntError ?
| Reporter | ||
Comment 2•23 years ago
|
||
You are right.
Happens if you copy and paste both phrases, but forget to copy the second time ;-)
Thanks for pointing out.
Well, what about this difference in spelling:
in the first "try" we have a "crl", in the second one we have "clr" - but in
both cases the "Updtae" were contained - so obviously it was _no_ copy and paste
- was it?
| Reporter | ||
Comment 4•23 years ago
|
||
Thanks Erik, I checked it out again.
The phrase in phonix is: crlAutoUpdtaeFreqCntError
^^^ ^^^^
Yes, there are two typos in one phrase.( If it's a typo; but I guess so)
I hadn't recognised the second typo and just copy and pasted the phrase then
corrected the first typo.
Sorry, for the confusion. It's about a month ago sine I reported the bug, and I
completely forgot about it.
Comment 5•23 years ago
|
||
Confirming
-->New
-->Bookmarks
Is this maybe in Mozilla as well? If so it should probably be reassigned to a
Mozilla component.
Assignee: blaker → chanial
Status: UNCONFIRMED → NEW
Component: General → Bookmarks
Ever confirmed: true
OS: Windows 2000 → All
| Reporter | ||
Comment 6•23 years ago
|
||
I just checked Mozilla 1.3a and you are right David: the typo is in Mozilla too.
It's the same path.
Comment 7•23 years ago
|
||
--> Over to Browser: Bookmarks
Assignee: chanial → ben
Product: Phoenix → Browser
QA Contact: asa → kasumi
Version: unspecified → Trunk
| Reporter | ||
Comment 8•23 years ago
|
||
Ok, now I figured out, that in crlAutoUpdtaeFreqCntError crl is right, but
Updtae is still a typo and I still can type a figure below 0, in the schedule
for bookmarks and it would still not complain.
This bug is very easy to fix. I'd have done it, if I'd know how to apply patches
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: bugs → nobody
QA Contact: kasumi → bookmarks
Comment 9•17 years ago
|
||
MASS-CHANGE:
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
Status: NEW → UNCONFIRMED
Comment 10•17 years ago
|
||
MASS-CHANGE:
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 11•17 years ago
|
||
MASS-CHANGE:
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 12•16 years ago
|
||
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
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•