Changes between Version 1 and Version 6 of Ticket #3249


Ignore:
Timestamp:
04/05/2016 06:07:50 PM (3 years ago)
Author:
sebastian
Comment:

As trev indicated above, the webNavigation API doesn't distinguish between actual popups and pages opened in a tab by the user. However It seems to be possible to identify popups by their windowType.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3249

    • Property Cc SMed79 kzar added
    • Property Component changed from Adblock-Plus-for-Firefox to Platform
    • Property Summary changed from Different behaviour firefox / chrome in treating the popups requests to Popup blocking is applied to pages opened by the user in a new tab
    • Property Priority changed from Unknown to P3
    • Property Owner set to sebastian
    • Property Ready set
  • Ticket #3249 – Description

    v1 v6  
    18182.try the same in firefox ==> no issue, the new tab will be opened. 
    1919 
    20 === Analysis === 
     20=== Expected behavior === 
    2121 
    22 Links being opened as new tab don't have `window.opener` property. That's why ABP/Firefox will ignore them, ABP/Chrome on the other hand doesn't check `window.opener`. 
     22Popup blocking filters should not cause tabs opened by the user to be closed.