ABP blocks too much on dict.leo.org

[Strulf]

EasyList influences the behaviour of links on the site. Some texts that are links are sometimes black instead of blue (for links) and you can’t click them. Certain links are still blue but you can never click them. For example if you search for “interactable”, which the site doesn’t find, it suggests you “intractable”. This should be clickable but with EasyList active, it’s not:

http://dict.leo.org/dictQuery/m-vocab/e … teractable

However, this only happens in Safari. In Chrome or Firefox, EasyList works fine. As well, Google would often show a wide page and hide everything when I use the browser’s back navigation after I clicked on a result. This only happens sometimes but it never happens with ABP deactivated.

[snoack]

I can't reproduce that. Which version of Safari and Adblock Plus are you using? Is EasyList your only filter list? Do you use a language specific version of EasyList? Do you have other extensions installed? Do you see any error in the JavaScript console?

[Strulf]

It seems to be EasyList Germany.

[snoack]

I can't reproduce it with EasyList Germany. So can you please answer my other questions from above?

[Wladimir Palant]

I cannot reproduce this either. In fact, getting to this page apparently requires disabling JavaScript - but then the link simply isn't clickable, Adblock Plus or not.

Edit: A look at the page source confirms - this isn't really a link so it cannot possibly work without JavaScript.

[Strulf]

JavaScript is on. There are other extensions, but I deactivated them completely, no change. Safari 7.0.3, ABP 1.8.1.1184 - as far as I know it’s still beta for Safari. EasyList is my only filter list. When it is deactivated, the link works, when it’s activated, the link can’t be clicked. EasyList Germany or not, I must have gotten this wrong before, it’s still only about EasyList, no other languages.

I get the console error “[Error] Error: cannot call methods on autocomplete prior to initialization; attempted to call method 'close'
error (dict.min-b8cec7c8.js, line 4)
(anonyme Funktion) (dict.min-b8cec7c8.js, line 140)
each (dict.min-b8cec7c8.js, line 4)
each (dict.min-b8cec7c8.js, line 4)
(anonyme Funktion) (dict.min-b8cec7c8.js, line 140)
stopSearchInput (dict.min-b8cec7c8.js, line 320)
search (dict.min-b8cec7c8.js, line 329)
onsubmit (de.html, line 1)”

And several links like dict.min-b8cec7c8.js:4:4135

When you type in “interactable” in a new dict.leo.org site, the link never works. When you refresh the site then however, the link works but doesn’t lead where it should go but opens and empty form again.

I don’t know, since I use ABP for Safari I have several strange problems. I just try to find out the reasons for this. Sometimes when I click on a Google search result and then go back to the results, the whole site would be just white. Refreshing the site shows the content again. This doesn’t happen with ABP deactivated either.

[Wladimir Palant]

JavaScript is on.

That's strange, with JavaScript on I get http://dict.leo.org/#/search=interactab ... wSingle=on as the URL - I can only get to the one you mentioned by deactivating JavaScript.

The Adblock Plus version you have installed is still a development build, yes. You can install the stable version from en/safari.

[Strulf]

Yes it’s odd, somethings off on this site. As I said, sometimes the link itself works but it doesn’t lead to the word ‘intractable’ although the address in the address bar would suggest so. It shows an empty form as if you just came to leo.dict.org freshly. Refreshing the site doesn’t help, but if I copy the link into a new tab the site is shown as expected. I don’t understand this and it doesn’t happen without ABP. I installed the stable version, still the same.

[Strulf]

OK terribly sorry guys, this was bothering me so much that I was checking everything again - turns out Glims seems to be the malefactor. Didn’t check that before since it is not in the list of extensions but has a separate menu item.

[j800r]

glims is still compatible with Safari 7?? The Safari changes were so drastic that glims in the state I remember would be totally unnecessary anyway. Ya, just looked on the site and the latest they mention is Safari 6 so I wouldn't use with Safari 7 anyway as it wouldn't be worth it.

(Apologies if this doesn't add much to the conversation).

[Strulf]

Check their FAQ, they say it’s tested with Safari 7: http://www.machangout.com/faq

[j800r]

hmm..you're right. But still, Safari 7 has most of those additional features and is fully coded in cocoa etc. I think Glims was better for more traditional Safari versions before the overhaul. Although that's partly opinion and i'm gonna shut up now as this has nothing to do with ABP and I don't wanna be told off.

[snoack]

I think it is interesting that most features that Glims provides can't be implemented with the extension API. And Safari 3 (the earliest version they support) didn't even had extensions. In fact Glims isn't actually implemented as an extension, but installs some binaries that somehow hook into Safari on a lower level. I'm curious how that works. But I didn't found any official documentation on that. Does anybody knows some implementation details?

[Strulf]

I agree, I don’t really need Glims anymore, I was just used to it. I deinstalled it right away when I realised that it was the reason for the strange behaviour in combination with ABP.

[Wladimir Palant]

On a quick glance it seems that Glims injects its library into Safari via DYLD_INSERT_LIBRARIES, not really an approach we would want to use. Other extensions were using Safari's binary plugin mechanism, not exactly easy either - the effort required would be comparable to Internet Explorer.