Closed Bug 177653 Opened 22 years ago Closed 14 years ago

[XBLFC] XBL form controls will need special handling so that they still work if JS is disabled.

Categories

(Core :: XBL, defect)

Product:
Core
Component:
XBL
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Milestone:
Future

People

(Reporter: bsharma, Assigned: jag+mozilla)

References

Details

This issue was reported after the Security review of XBL, jag asked me to make a bug out of the issue.
bryner said "I don't see XBL form controls happen anytime soon".
Target Milestone: --- → Future
Since the feature is not in use, this is not a security issue so I will open this to the public. Naturally this bug will need to be addressed before XBL form controls will be turned on.
Group: security?
59701 talks about a new security policy for XBL that would involve privileges coming from the binder rather than the document to which you're bound. This would mean that a binding attached via a UA sheet (a trusted UA sheet) would be privileged regardless of where it was bound. The problem of course is that I could promptly think of numerous exploits if we went to that policy. Anyway, a simple hack solution would be to just add a special attribute to the XBL file that indicates that its JS cannot be disabled.
Depends on: 59701
OS: Windows 2000 → All
Hardware: PC → All
Summary: XBL form controls will need special handling so that they still work if JS is disabled. → [XBLFC] XBL form controls will need special handling so that they still work if JS is disabled.
QA Contact: ian → xbl
XBL form control bugs are no longer *especially* relevant to anyone.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.