Firefox3.1/SMIL Security Review: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 35: Line 35:
The contents of the SVG/SMIL <animate> / <set> / <animateTransform> element's attributes.  These consist of semicolon-separated lists of values, time values,
The contents of the SVG/SMIL <animate> / <set> / <animateTransform> element's attributes.  These consist of semicolon-separated lists of values, time values,
   
   
The SMIL patch adds a "nsSMILParserUtils" class that takes care of its parsing needs.
The SMIL patch adds the class "nsSMILParserUtils," which takes care of its parsing needs.


* What is the output of this feature
* What is the output of this feature

Revision as of 17:45, 3 September 2008

Overview

Describe the goals and objectives of the feature here.

Background links

Security and Privacy

  • What security issues do you address in your project?

None.

  • Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?

No. (Only one pref, to enable/disable SMIL support.)

  • Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.

Exported APIs

  • Please provide a table of exported interfaces (APIs, ABIs, protocols, UI, etc.)
  • Does it interoperate with a web service? How will it do so?
  • Explain the significant file formats, names, syntax, and semantics.
  • Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully?
  • Does it change any existing interfaces?

Module interactions

  • What other modules are used (REQUIRES in the makefile, interfaces)

gfx, layout, content

Data

  • What data is read or parsed by this feature

The contents of the SVG/SMIL <animate> / <set> / <animateTransform> element's attributes. These consist of semicolon-separated lists of values, time values,

The SMIL patch adds the class "nsSMILParserUtils," which takes care of its parsing needs.

  • What is the output of this feature

Animations (animated attributes) in SVG documents that would otherwise be static.

  • What storage formats are used

Reliability

  • What failure modes or decision points are presented to the user?
  • Can its files be corrupted by failures? Does it clean up any locks/files after crashes?

Configuration

  • Can the end user configure settings, via a UI or about:config? Hidden prefs? Environment variables?
  • Are there build options for developers? [#ifdefs, ac_add_options, etc.]
  • What ranges for the tunable are appropriate? How are they determined?
  • What are its on-going maintenance requirements (e.g. Web links, perishable data files)?

Relationships to other projects

Are there related projects in the community?

  • If so, what is the proposal's relationship to their work? Do you depend on others' work, or vice-versa?
  • Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?

Review comments

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox3.1/SMIL_Security_Review&oldid=107254"