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

Issue 840448 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Feature

Blocking:
issue 792774



Sign in to add a comment

Refactor offline_internals.js to eliminate `var` usage

Project Member Reported by carlosk@chromium.org, May 7 2018

Issue description

Status: Available (was: Untriaged)
Do we need to do anything here?

We think we tried to do this before, and the linter complained that it would break iOS.  However, it seems unlikely we will make the feature for iOS.
Cc: dpa...@chromium.org
+dpapad@ who suggested this to see if he has comments on this potential iOS issue.
Can you paste the exact error you encountered? Was it coming from [1]? This check should only be checking some shared JS code locations (locations that might potentially hold iOS code) for potential iOS breakages. If you are sure that the feature is not used in iOS, even though the code is residing such a location, you can ignore the warning and proceed.

[1] https://cs.chromium.org/chromium/src/PRESUBMIT.py?type=cs&q=_CheckForRiskyJsConstLet+-file:third_party+-file:infra+-file:out/Debug&l=2545
Status: WontFix (was: Available)
WontFix, as per #3
Status: Available (was: WontFix)
offline_internals.js still uses var. Comment#3 implies that the PRESUBMIT warning can be ignored since offline_internals is not used on iOS, therefore this bug is still relevant.
Blocking: 792774
Labels: Hotlist-Fixit

Sign in to add a comment