Page 1 of 1

[WorksForMe] AdBlock+ crashes Chrome web inspector

Posted: Sun Mar 18, 2012 6:55 pm
by yellowled
* AdBlock Plus (Beta) 1.2 – standard config w/ EasyList Germany+EasyList and Recommended filters for Google Chrome
* Google Chrome 17.0.963.79
* Ubuntu 11.10

To reproduce:

1. Open any web page
2. Inspect any page element with web inspector
3. In web inspector under "Styles", click "New Style Rule" (the + sign)
4. Hit <TAB> (usually skips from selector to style rules for said element; same thing happens if you do anything after creating a new rule)
→ "Aw, Snap!" error page

I realize this may never bother the John Doe user, but it's *very* annoying for web developers.

If you need any further testing etc., I'm happy to help.

Regards
Matthias

Re: AdBlock+ crashes Chrome web inspector

Posted: Mon Mar 26, 2012 11:07 am
by Wladimir Palant
I can reproduce it in Chrome 17 with Adblock Plus 1.2. The good news: they fixed it in Chrome 18, no crash there. Also, the current Adblock Plus development build no longer triggers this issue (we changed the way how styles are being injected into the page).

Marking as WorksForMe, will be fine with the next Chrome or Adblock Plus release - whichever comes first.

Re: AdBlock+ crashes Chrome web inspector

Posted: Thu Apr 19, 2012 5:31 pm
by yellowled
Wladimir Palant wrote:The good news: they fixed it in Chrome 18, no crash there.
The bad news: Did work fine in Chrome 17, does not work again in Chrome 18, but differently. It no longer shows the "crash page", but I'm unable to use web inspector's "New Style Rule" function. Any style I enter gets deleted/not accepted after entering it.

Chrome 18.0.1025.162 on Ubuntu 11.10, AdBlock+ 1.2.

Re: [WorksForMe] AdBlock+ crashes Chrome web inspector

Posted: Fri Apr 20, 2012 7:23 am
by Wladimir Palant
Please try the development build.

Re: [WorksForMe] AdBlock+ crashes Chrome web inspector

Posted: Fri Apr 20, 2012 1:35 pm
by yellowled
With the dev build (1.2.0.774), it works.

Re: [WorksForMe] AdBlock+ crashes Chrome web inspector

Posted: Fri Apr 20, 2012 6:52 pm
by yellowled
I'm sorry, I have to correct that: It does not work with the development build, either. Not sure why it seemed to work in my initial test, but it does not, at least not reliably.

YL