New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 767058 link

Starred by 4 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Task



Sign in to add a comment

Convert StrictMode usage to StrictModeContext

Project Member Reported by estevenson@chromium.org, Sep 20 2017

Issue description

We should convert all StrictMode usages to StrictModeContext for readability code health reasons. At the same time, the conversion process will require going through each StrictMode violation, which is a good opportunity to audit and remove obsolete code. 

The three main categories of StrictMode violations are (from wnwen@):

1. Third party code that we can't modify.
2. Too hard/too much work to fix.
3. White-listed but actionable and we should still try to fix them.

We might also consider adding separate methods for each of these categories to make tracking easier.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 20

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Type-Bug Type-Task

Sign in to add a comment