Chrome 69 breaks the extension?
Closed this issue · 12 comments
I just received this over email:
Ever since the chrome 69 update, search engines are getting through the filter. Specifically Yahoo! & AOL. Still a great app and there are far fewer SE's to clean out now, however, I would love if you could find a way to block these too.
I'm running the latest from @Procyon-b (#17) and it seems to block AOL and Yahoo OK in a quick test. I still haven't had a chance to do a complete test, but do you think it's worth deploying anyway? If so, either of us can merge it.
Yeah, I'd love to do this in the next few days. I couldn't find the time to do this earlier unfortunately.
I just ran down the list on the wiki and tried one search on each - looks OK to me. I have merged and it is ready for you to tag and release.
I have also tested against sites in this list, and it works ok.
Those using the extension have a very old version of the script. Without the aol and duckduckgo fixes.
As a sidenote, has one of you been able to prevent chrome from updating?
I have talked about this with a friend this week-end, and he told me that he can (he is under win10).
Anyway, I was able to get rid of material design, so...
I have not been able to prevent the update. At this point I am resigned to breakage. I try to use only extensions that are either actively supported by a large organization, or open-source so I can fix them :) .
When I heard that chrome 69 was introducing an interface redesign to material design, I was a little bit worried. I have seen sites becoming almost unusable after (badly) moving to material design principle.
I don't have a link to it anymore, but I have seen one, with an almost empty page, except for a logo, a couple of link, and a big input field. The input field was hardly visible: white on a white page, without colored border, and a small very light grayish shadow under a small part of the bottom right corner, and no autofocus.
Then I saw the redesign of the web store...
But thanks to the flags page, I'm able to continue using chrome with pre-69 design. :)
Yurk.
But if it's like the removing of the "www." prefix in the first version of 69, it will be short-lived. By the time my chrome decided to upgrade (v ..92 on 13 sep) it was already disabled.
And thanks to chrome://flags/ many options can be modified.
@gregsadetsky We can close this, right? I see you did a release on Sep. 25
@gregsadetsky @Procyon-b Any interest in joining me in a GitHub organization for Chrome extensions? My TabFern extension is getting big enough to benefit from one, and I thought if you were interested I could create one and we could host both of our extensions there. Any thoughts either way?
@cxw42 I think that we can close this, yes! Thank you
Re: Org -- what would it entail? What are the benefits? Don't hesitate if you want to discuss in private -- gs at gregsadetsky dot com
Cheers and Happy Holidays! :-)
@cxw42, as @gregsadetsky said, I have no idea of what is a "GitHub organization".
Follow-up of my comment/question above : after chrome 71 has been out, I have found a solution to prevent chrome updates. I'm now happily using 70.0.3538.110 without chrome forcing me the new version.