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

Issue 9496013: Pop-up blocking functionality for Chrome (Closed)

Created:
March 1, 2013, 3:45 p.m. by Wladimir Palant
Modified:
March 5, 2013, 2:41 p.m.
Reviewers:
Thomas Greiner
Visibility:
Public.

Description

This tries to reproduce the pop-up blocking behavior for Firefox - first we check whether about:blank is allowed to be opened, then whether the actual target URL is allowed.

Patch Set 1 #

Total comments: 1

Patch Set 2 : Fixed wrong return statement #

Patch Set 3 : Use webNavigation API rather than tabs API (see issue 13021) #

Unified diffs Side-by-side diffs Delta from patch set Stats (+12 lines, -17 lines) Patch
M metadata.chrome View 1 2 1 chunk +1 line, -0 lines 0 comments Download
M popupBlocker.js View 1 2 1 chunk +11 lines, -17 lines 0 comments Download

Messages

Total messages: 5
Wladimir Palant
March 1, 2013, 3:45 p.m. (2013-03-01 15:45:54 UTC) #1
Thomas Greiner
LGTM, only a cosmetic change http://codereview.adblockplus.org/9496013/diff/1/popupBlocker.js File popupBlocker.js (right): http://codereview.adblockplus.org/9496013/diff/1/popupBlocker.js#newcode29 popupBlocker.js:29: return false; inconsistent with ...
March 4, 2013, 11:28 a.m. (2013-03-04 11:28:02 UTC) #2
Wladimir Palant
March 4, 2013, 11:46 a.m. (2013-03-04 11:46:47 UTC) #3
Wladimir Palant
March 5, 2013, 12:14 p.m. (2013-03-05 12:14:29 UTC) #4
Thomas Greiner
March 5, 2013, 12:55 p.m. (2013-03-05 12:55:24 UTC) #5
LGTM

Powered by Google App Engine
This is Rietveld