Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Issue 8691076: Make sure to indicate to Chrome when our filters change (Closed)

Created:
Oct. 29, 2012, noon by Wladimir Palant
Modified:
Oct. 30, 2012, 11:12 a.m.
Reviewers:
Thomas Greiner
Visibility:
Public.

Description

See http://developer.chrome.com/extensions/webRequest.html#caching - it seems that we should be calling handlerBehaviorChanged() whenever our filters change.

Patch Set 1 #

Total comments: 1

Patch Set 2 : #

Total comments: 1

Patch Set 3 : #

Unified diffs Side-by-side diffs Delta from patch set Stats (+29 lines, -0 lines) Patch
M webrequest.js View 1 2 1 chunk +29 lines, -0 lines 0 comments Download

Messages

Total messages: 7
Wladimir Palant
Oct. 29, 2012, noon (2012-10-29 12:00:11 UTC) #1
Thomas Greiner
Please check if it's possible for a user to somehow trigger multiple triggers shortly after ...
Oct. 29, 2012, 4:40 p.m. (2012-10-29 16:40:16 UTC) #2
Wladimir Palant
Ok, I've added a delay.
Oct. 30, 2012, 9:52 a.m. (2012-10-30 09:52:02 UTC) #3
Thomas Greiner
one quick change left http://codereview.adblockplus.org/8691076/diff/1002/webrequest.js File webrequest.js (right): http://codereview.adblockplus.org/8691076/diff/1002/webrequest.js#newcode47 webrequest.js:47: window.setTimeout(onFilterChange, 2000); set onFilterChangeTimeout variable ...
Oct. 30, 2012, 10:17 a.m. (2012-10-30 10:17:22 UTC) #4
Wladimir Palant
Heh, I wonder why it seemed to work when I tested it.
Oct. 30, 2012, 10:41 a.m. (2012-10-30 10:41:08 UTC) #5
Thomas Greiner
On 2012/10/30 10:41:08, Wladimir Palant wrote: > Heh, I wonder why it seemed to work ...
Oct. 30, 2012, 10:47 a.m. (2012-10-30 10:47:37 UTC) #6
Thomas Greiner
Oct. 30, 2012, 10:47 a.m. (2012-10-30 10:47:59 UTC) #7
LGTM

Powered by Google App Engine
This is Rietveld