Firefox 3.6/System Metrics Security Review: Difference between revisions

Jump to navigation Jump to search
more information
(fill out part of the template)
 
(more information)
Line 4: Line 4:
;Background links
;Background links
* feature-tracking bug links
* feature-tracking bug links
** [http://hg.mozilla.org/mozilla-central/log/8eabb8863ad6/widget/public/nsILookAndFeel.h history of nsILookAndFeel.h]
** {{bug|384612}}: Get rid of script in scrollbar XBL binding
*** introduced ''':-moz-system-metric()'''
*** added '''scrollbar-start-backward''' metric
*** added '''scrollbar-start-forward''' metric
*** added '''scrollbar-end-backward''' metric
*** added '''scrollbar-end-forward''' metric
*** added '''scrollbar-thumb-proportional''' metric
** {{bug|415810}}: Respect the user's settings of icons in menus
*** added '''images-in-menus''' metric
** {{bug|426660}}: Allow Firefox themes to change based on the OS theme
*** added '''windows-default-theme''' metric
** {{bug|418454}}
*** added '''windows-compositor''' metric
** {{bug|431666}}}
*** added '''windows-classic''' metric
** {{bug|448767}}
*** added '''mac-graphite-theme''' metric
** {{bug|503042}}
*** added '''touch-enabled''' metric
** {{bug|520341}}
*** added '''maemo-classic''' metric
** {{bug|509671}}
*** added '''images-in-buttons''' metric
** {{bug|522149}}: Add CSS media queries for all features supported in :-moz-system-metric()
* specs or design docs
* specs or design docs


== Security and Privacy ==
== Security and Privacy ==
* Is this feature a security feature?  If it is, what security issues is it intended to resolve?
* Is this feature a security feature?  If it is, what security issues is it intended to resolve?
** feature
** no
* What potential security issues in your feature have you already considered and addressed?
* What potential security issues in your feature have you already considered and addressed?
** none
** none
Line 14: Line 39:
** N/A
** N/A
* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.
* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.
** primary risk is making available information about a user's system that either (1) the user wouldn't want known or (2) could be used to improve the quality of certain spoofing attacks
* How are transitions in/out of Private Browsing mode handled?
* How are transitions in/out of Private Browsing mode handled?
** not handled
** not handled
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334

edits

Navigation menu