default preferences are incorrect for Photon/Neutrino

VERIFIED FIXED in mozilla0.9.6

Status

SeaMonkey
Preferences
P3
normal
VERIFIED FIXED
17 years ago
14 years ago

People

(Reporter: Brian Edmond, Assigned: Samir Gehani)

Tracking

Trunk
mozilla0.9.6
All
Neutrino

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

17 years ago
The default preferences for Photon/Neutrino are incorrect.
(Reporter)

Comment 1

17 years ago
Created attachment 43248 [details] [diff] [review]
fixes default preferences for Neutrino/Photon (adds photon.js)
Keywords: patch, qawanted

Comment 2

17 years ago
The attached file photon.js contains 3 copies of the same set of preferences...
Auto fire pasting? :)

Also, the build changes look wrong to me. It looks like you've replaced unix.js
with photon.js instead of adding to unix.js as the openvms case below does.

Comment 3

17 years ago
Created attachment 47019 [details] [diff] [review]
updated patch file fixes bad photon.js

Comment 4

17 years ago
Much better, and I was wrong about the build changes. They are ok as well.
r=bnesse.

Comment 5

17 years ago
targetting 096/p3, pending sr
Priority: -- → P3
Target Milestone: --- → mozilla0.9.6
(Assignee)

Comment 6

17 years ago
Brian (Edmond),
Get an sr and I'll check it in for you on the trunk.

Updated

17 years ago
Attachment #43248 - Attachment is obsolete: true

Comment 7

17 years ago
Comment on attachment 47019 [details] [diff] [review]
updated patch file fixes bad photon.js

Added review to patch status.
Attachment #47019 - Flags: review+
Comment on attachment 47019 [details] [diff] [review]
updated patch file fixes bad photon.js

sr=jst
Attachment #47019 - Flags: superreview+

Comment 9

17 years ago
checked into TRUNK

Comment 10

17 years ago
Marking fixed as per Dave's comment.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
rs vrfy by checking lxr.
Status: RESOLVED → VERIFIED
Keywords: qawanted
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.