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

Issue 6136997097766912: Fallback to the top-level frame if we don't know the frame on Chrome (Closed)

Created:
Jan. 23, 2014, 8:57 a.m. by Sebastian Noack
Modified:
Jan. 23, 2014, 10:17 a.m.
Visibility:
Public.

Description

Frames with javascript: or data: URL bypass Chrome's webrequest API. In addition to not being able to block those frames they currently break the frame hierarchy we rely on for some blocking and whitelisting rules. This is a regression in the current devbuild. Before we just assumed to be in the top-level frame when encountering an unknown frame. This isn't optimal but fixes at least most domain-based filter rules. So I have added that approach again.

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+15 lines, -4 lines) Patch
M chrome/ext/background.js View 1 chunk +15 lines, -4 lines 0 comments Download

Messages

Total messages: 3
Sebastian Noack
Jan. 23, 2014, 9:02 a.m. (2014-01-23 09:02:34 UTC) #1
Felix Dahlke
LGTM
Jan. 23, 2014, 9:09 a.m. (2014-01-23 09:09:51 UTC) #2
Wladimir Palant
Jan. 23, 2014, 10:17 a.m. (2014-01-23 10:17:22 UTC) #3
LGTM

Powered by Google App Engine
This is Rietveld