Closed
Bug 163913
Opened 23 years ago
Closed 23 years ago
[typeaheadfind] status messages no longer displayed
Categories
(SeaMonkey :: Find In Page, defect)
SeaMonkey
Find In Page
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
Attachments
(1 file)
|
2.65 KB,
patch
|
yuanyi21
:
review+
alecf
:
superreview+
|
Details | Diff | Splinter Review |
Type ahead find used to display status messages, and it no longer does.
The problem happens because
"chrome://typeaheadfind/locale/typeaheadfind.properties"
is getting expanded to
"/moz/mozilla/dist/bin/chrome/locales/en-US/typeaheadfind.properties"
I'm convinced this happened when I created split typeaheadfind into resources,
src and public directories.
|
Assignee | |
Updated•23 years ago
|
|
|
Assignee | |
Comment 1•23 years ago
|
||
I'm sure it's something stupid.
When I tried to get get the strings, it goes to load typeaheadfind.properties,
and that load fails.
It's returning early out of that function at nsChromeRegistry::GetBaseURL at
this line:
http://lxr.mozilla.org/seamonkey/source/rdf/chrome/src/nsChromeRegistry.cpp#658
|
|
Assignee | |
Comment 2•23 years ago
|
||
Seeking r=/sr=
|
||
Comment 3•23 years ago
|
||
Comment on attachment 96267 [details] [diff] [review]
I needed a second contents.rdf - of course!
sr=alecf
Attachment #96267 -
Flags: superreview+
Comment on attachment 96267 [details] [diff] [review]
I needed a second contents.rdf - of course!
r=kyle
Attachment #96267 -
Flags: review+
|
|
Assignee | |
Comment 5•23 years ago
|
||
checked in
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
|
|
||
Comment 6•23 years ago
|
||
vrfy'd fixed with 2002.09.24.08 mozilla trunk. status msgs are present.
Status: RESOLVED → VERIFIED
|
||
Updated•18 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•