-
-
Notifications
You must be signed in to change notification settings - Fork 784
@secure decorator. #6549
Copy link
Copy link
Closed
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developersp4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Milestone
Metadata
Metadata
Assignees
Labels
audience/nvda-devPR or issue is relevant to NVDA / Add-on developersPR or issue is relevant to NVDA / Add-on developersp4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Type
Fields
Give feedbackNo fields configured for issues without a type.
Background:
This copy-paste code is all over the place. I propose an @secure decorator in NVDA that can help ensure NVDA never runs on secure screens in a decorated method.
Advantages: @secure could be updated in the future if new security related things are added. This would prevent shot gun surgery from needing to be performed with said feature being added. Addons could use this by default.