Open Bug 1437649 Opened 6 years ago Updated 2 years ago

wpt lint triggers on setTimeout() in a comment

Categories

(Testing :: web-platform-tests, enhancement)

Version 3
enhancement

Tracking

(Not tracked)

People

(Reporter: bkelly, Unassigned)

Details

Over in bug 1436763 I ran into a wpt linting failure because I added this comment to a file:

// Registers, waits for activation, then unregisters on a dummy scope.
//
// This can be used to wait for a period of time needed to register,
// activate, and then unregister a service worker.  When checking that
// certain behavior does *NOT* happen, this is preferable to using an
// arbitrary setTimeout() delay.

Its somewhat ironic that my comment about avoiding arbitrary setTimeout() triggered the lint rule intended to block setTimeout().  I don't know if its possible to make this smarter or not, but it might be nice.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.