(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

Just to help you a bit: this are the (not yet blocked_on) issues which bother us the most:
issue 60101 issue 60435 issue 65110 issue 68705  issue 81298  issue 82804

Thanks. I'll add them to the list.

Can you give us a little context about the relative pain these are causing?  For instance, it looks like issue 68705 has been worked around (which doesn't mean it's not a bug, of course), which means fixing it isn't as big a win. How do the others effect users in a concrete way?

That sort of information helps us triage bugs properly.

In order from most to least impact:

60101: Biggest feature ever.
60435, 65110, 81298: Rarely effects users; it doesn't happen often.  AdBlock has lived with these for a while now.
68705: AdBlock must work around this on a site-specific basis.
82804: Basically no impact; AdBlock works around this.

60101: agree with Michael
60435, 65110, 81298: when these happen, we have to disable parts of the code (like context menus) for those sites as we need the data from X.tab(s) for the code. Also, I don't know how much additional coding it'll require to fix https://code.google.com/p/adblockforchrome/issues/detail?id=5924#c22
68705: agree with Michael. We must work around it, but then it first has to be reported. I don't know how many sites exist with that issue that simply haven't been reported yet (because users didn't know how to report it, or didn't notice it was due to AdBlock instead of a site issue)
82804: simply causing scripting errors on some sites (including acid3 and the one mentioned in that issue). Running the code twice = spending twice the time to parse everything. But it indeed has no visual impact. @Michael, we don't have a workaround. adblock.js (not adblock_start.js) simply aborts because an variable doesn't exist anymore, but filter parsing etcetera has already happened by then.

(No comment was entered for this change.)

Thanks guys. I'll feed this back to the extensions team.

New blocker:  issue 96442 . "Let extensions detect whether they were externally installed"

I don't think 96442 is AdBlock specific, all extensions could use it and it isn't related to adblocks goal: blocking ads.
 issue 96544  however is.

Adding issue 97392: "[It's] Hard to inform a DOM element that it's been blocked" and  issue 96544 : "AdBlock creates 70 megs of JavaScript string data on mashable.com" (although that latter needs no triage: it's well prioritized already).

Regarding  issue 96442 , however, Michael pointed to it as an interesting feature he'd like to see implemented, but you're right, it's not at all adblock-specific. It doesn't have to be... this wrap-up bug is really just so I can help triage requests internally. :)

Adding  issue 98048 : "No way to get parent frame ID of <iframe> in webRequest.onBeforeRequest"

Adding  issue 103018 : "Defective Origins/CURRENT file disables File System API" (which was reported by AdBlock Plus, not AdBlock, just so we know who to talk to).

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

Adding  Issue 109272 : "In canary, document.documentElement is null at document_start"

 issue 108942  and  issue 109352  can be added too, since tabs.getSelected is deprecated and we have to start using tabs.query(...)

Adding  Issue 109352 : 'chrome.tabs.query returns tabs[0].url === "" for target="blank" links when fired from tabs.onSelectionChanged' and  Issue 108942 : 'chrome.tabs.query required a windowId'

Er. Actually adding those issues as blockers. :)

And  issue 108198  - Permission upgrade detection seems incorrect, which prevents us from enabling popup blocking by default.

Added.

Adding  issue 110084 : 'el.style.prop = "val !important" fails'

Adding Issue #111623: "After an extension update, extension broken for a small percentage of users"

Adding  Issue #115714 : `chrome.i18n.getMessage` error.

Also  issue 55136  (we experience this issue with some images and iframes)
(this issue would also be moot, just like some others, if issue 97392 is fixed, but currently it's still a bug for us)

Adding:

- #115138: "WebNavigation/tabs: nonexistent tab IDs in onCommitted listener"
- #55136: "Image not send through 'beforeload' handler"

I just filed issue 120362 which is also useful for AdBlock.

Adding issue 120362: "webRequest blocking iframe: you'll have to press the back button twice"

issue 123476 will help us to distinguish between 'the-website-requested' and 'the-user-requested' new tabs.
Although this isn't a very big issue (users would be clicking an ad link anyway), it'd be nice if we were able to really just filter the former of the two.

(No comment was entered for this change.)

Adding issue 124989, "Extension's content scripts should be allowed to ignore CSP and web_accessible_resources"

Adding  issue 124988 , "Content security policy shouldn't block about:blank"

I don't know if regressions in the browser affecting AdBlock should also be mentioned here, but if so, I'd like to nominate  issue 128347  

(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)