search

pb6110 / scriptno

Automatically exported from code.google.com/p/scriptno
0 stars 0 forks source link

Experimental ScripNo blocks the work of AdBlock Plus. #13

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install Experimental ScripNo.
2. Install Experimental AdBlock Plus ( 
https://adblockplus.org/devbuilds/adblockpluschrome-experimental/ )
3. AdBlock Plus doesn't work

Please add to the exceptions AdBlock Plus.

What version of the product are you using? On what operating system?
Experimental ScripNo 10544
Experimental AdBlock Plus 1.1.4.695
OS Windows XP SP3

Original issue reported on code.google.com by racersvb@gmail.com on 30 Sep 2011 at 2:14

GoogleCodeExporter commented 8 years ago 
Sorry,
Browser - Google Chrome 16.0.895.0 canary

Original comment by racersvb@gmail.com on 30 Sep 2011 at 2:36

GoogleCodeExporter commented 8 years ago 
Try to change default mode to "allow" in ScriptNo settings.

Original comment by adi...@gmail.com on 30 Sep 2011 at 4:53

GoogleCodeExporter commented 8 years ago 
With ScriptNo v1.0.5.44 Experimental and Chrome 14.0.835.186 i CAN'T reproduce 
it ...

Have you the latest AdBlock Plus Experimental from URL 
https://adblockplus.org/en/development-builds#installation installed?

Greetings
SwissBIT

Original comment by swiss...@bluemail.ch on 30 Sep 2011 at 11:46

GoogleCodeExporter commented 8 years ago 
Oh, sorry, i see you have the latest ADB, maybe it's a problem with your Chrome 
Experimental ... have you try it with the Chrome stable?

Original comment by swiss...@bluemail.ch on 30 Sep 2011 at 11:49

GoogleCodeExporter commented 8 years ago 
Stable does not support the WebRequest API.
AdBlock then works fine if I turn off SkriptNo.

Original comment by racersvb@gmail.com on 1 Oct 2011 at 5:57

GoogleCodeExporter commented 8 years ago 
Stable DOES support WebRequest-API as experimental version (since Chrome 14 
beta i had read) - not "out-of-the-box" and not sure, if it's the LATEST API, 
but with URL chrome://flags you can enable it.

Greetings
SwissBIT

Original comment by swiss...@bluemail.ch on 1 Oct 2011 at 3:08

GoogleCodeExporter commented 8 years ago

Original comment by andr...@gmail.com on 14 Nov 2011 at 3:56

GoogleCodeExporter commented 8 years ago 
Reproduced (it's an issue with Chrome) and I'm discussing this issue with 
Chrome devs who do have a rough idea on how to solve this: 
https://code.google.com/p/chromium/issues/detail?id=90843#c17

Original comment by andr...@gmail.com on 17 Nov 2011 at 2:42

GoogleCodeExporter commented 8 years ago 
Issue 19 has been merged into this issue.

Original comment by andr...@gmail.com on 17 Nov 2011 at 2:43

GoogleCodeExporter commented 8 years ago 
Issue 28 has been merged into this issue.

Original comment by andr...@gmail.com on 17 Nov 2011 at 2:45

GoogleCodeExporter commented 8 years ago 
Linked vs Inline scripts? Can Chrome differentiate between the two? If it can 
this should be fixable.

Original comment by ColinTre...@gmail.com on 19 Dec 2011 at 6:32

GoogleCodeExporter commented 8 years ago 
Just an update: this seems to be fixed with the stable releases of WebRequest 
and ContentSettings :) I'll continue testing.

Original comment by andr...@gmail.com on 15 Feb 2012 at 5:31