Closed Bug 7254 Opened 21 years ago Closed 21 years ago
Implement DOM security
Entering all security bugs and tasks for SeaMonkey into Buzilla for schedule tracking.
This is mostly done but a little unstable (like I know I'm leaking right now). I don't think we gain a lot dropping this in now so I'm going to put it into M8 instead and play on local trees for another week.
Status: NEW → ASSIGNED
Target Milestone: M7 → M8
This is partially fixed but not fully functional. Checking in what I have now and moving bug to M9 for further work.
This is still in a partial state. Moving to M10 for further work.
Adding dependency on 12957, pushing back target milestone to M11.
DOM security can be enabled by changing mozilla/modules/libpref/src/win/winprefs.js so that security is enabled by changing the line /* DISABLE FOR NOW to ///* DISABLE FOR NOW and similarly for the comment close. Rebuild so the changed file is copied to dist. This causes incorrect errors as found in 13192 and 12957
Summary: Implement DOM security; Bell Labs code integration → Implement DOM security
Changed summary to remove "Bell Labs code integration". That's all under bug 858.
Do we really need this for the mozilla beta?
Yes, we need this for beta. The current beta criteria involve enabling e-commerce by protecting credit card information on form submission, for which we need this bug fixed.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Checked in changes that enable DOM security checks.
Norris Boyd, Could you please verify this one ?
You need to log in before you can comment on or make changes to this bug.