David Hyatt wrote:
>
> Maybe you could condense this and post it into the bug, so we don't
> forget what was decided here.
Done.
Next question - what would it take to actually implement this change in
security model? When might it happen? And is there anything that, as a
non-mozilla-guru, I can do to help?
>From an outsider's perspective, I can think of the following
pre-requisites:
1) Add a parameter to whatever function/method adds a stylesheet to a
document which takes a security principal to associate with this
association. Modify all callers to pass that parameter (in particular,
making sure that normal <link>, <style src> and <?xml-stylesheet?> pass
the document's security principal, but that whatever adds html.css
passes a trusted principal).
2) Store the resulting principal somewhere (is there even a structure
associated with the linkage between a stylesheet and a document? If not,
where do we store this?)
3) Do whatever is necessary to use this principal for XBL added by that
stylesheet (does a binding even know what CSS file added it?)
4) Make sure that html.css and similar files are not accessible through
CSSOM.
Like I said, I'm not a mozilla, style system, XBL, or C++ guru (the
extent of my patching is a 13-line-deletion in nsStdURL) but I'm quite
willing to have a stab at this if it's within my skills and if you can
give me some pointers as to where to start. If not, I'll do anything
else I can to help.
Stuart.
