Security/Features/XSS Filter: Difference between revisions

no edit summary
No edit summary
Line 38: Line 38:
== Release Requirements  ==
== Release Requirements  ==


*Complete C++ implementation
*There must be a way for sites (and users) to disable/enable this feature.
*Test the feature in the beta channel and assess its compatibility with existing websites.
*Incurred overhead must be minimal and acceptable for performance.
*We must have a minimal occurrence of induced false positives
*We must have a robust test suite and plan for testing effects of this feature.


== Next Steps & Open Issues  ==
== Next Steps & Open Issues  ==


*What is the average overhead of the filter? Can we use telemetry to find this out?
*{{ok|Complete C++ implementation}}
*Can we do anything about induced false positives?
*{{new|Test the feature in the Aurora channel to assess its compatibility with existing websites.}}
<!--
*{{new|Measure the average overhead of the filter?}} (Can we use telemetry to find this out?)
 
== Related Bugs &amp; Dependencies  ==
== Related Bugs &amp; Dependencies  ==


Links to the feature tracking bug &amp; other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.  
Links to the feature tracking bug &amp; other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.  


<!--
== Risks  ==
== Risks  ==


Line 66: Line 70:
Any and all test plans and strategies. Either inline or linked to.  
Any and all test plans and strategies. Either inline or linked to.  
-->
-->
== Goals  ==
== Goals  ==


canmove, Confirmed users
1,537

edits