Any ideas why this extension was marked dangerous and removed from the Chrome store? It happened ~ 10 days ago.
You can try and ask the team from digging around on their github repo. It could be that it's not being maintained. It doesn't look like it's had any updates in like 7 years...
Related
I've recently released a new version of my extension as V3.
Since the day I released the extension, I see that older versions of my extension are gaining more users. This is super weird. I haven't done anything with older versions, and I can clearly see in the Chrome Web Store statistics of weekly users, that there is a rise in the number of users, right when my extension was released with MV3. This can't be a coincidence.
Did anyone else see this? Any idea why this is happening? I want all of my users to be on the latest version of my extension, especially on the MV3 one.
I tried looking around the web for answers, but couldn't fin d anyone with this issue.
I know it sounds funny, because who would complain about having more users, but I really want to understand why this is happening.
Thanks
How much time will it take for Google to finish its review for a extension before it gets published to the Chrome Web Store?
Review times vary; some reviews complete in a few hours, others take many days, and in some cases a review can take several weeks
https://developer.chrome.com/webstore/faq#faq-listing-108
Long time no review, many days, few weeks. Our users can't wait. This is reason why we moved almost feature of extension from Chrome Extension to our own app
So it's weird. The review now take 10 days because they review all versions like its new. So if you make a push and have a small fix it's another 10 days. And sometimes it is more than 10 days.
This means a different strategy towards trying to get your extension deployed. First we are setting up a testing item in the Chrome Store Dev Section so that we can test our extension extensively in Chrome.
Second we are looking at using eval() in order to put our code in a wrapper. We already do this for FF and Safari. The real goal is to move more and more of the processing to the back end so that the need for a deployment becomes rarer.
This sounds like a lot of hoops but if you look at it from Chrome's end and the issues they have had around people doing bad things with extensions this is the price that has to be paid in order to be able to make extensions from their point of view.
This question already has answers here:
How to stop Chrome from redirecting to HTTPS?
(5 answers)
Closed 5 years ago.
From last update of Google Chrome 63.0.3239.84 the .dev domain of my local development machine does not work anymore becouse the browser force URL over https and I do not have a sicure certificate on my local machine. Is there a way to make it work with .dev?
I do not want to use other domains like .local or .test
I tried to enable/disable this chrome://flags/#allow-insecure-localhost but nothing.
You shouldn't change it.
Since 1999 that the Network Working Group(NWG) wrote a memorandum listing the safe Top Level Domains(TLDs) for development.
Choose one of that list to have a future-proof solution.
Because some developers depend on some tools with this poor approach - I was one of them - you can use a hack to solve this: write badidea when the HSTS warning pops up.
Use this only as a temporary solution and dedicate your time upgrading, or helping upgrade, your tools.
EDIT: Other solutions here.
No, there is no workaround to make .dev work in Chrome; it now belongs to Google.
https://laravel-news.com/chrome-63-now-forces-dev-domains-https
We are using this widget: http://captivatedev.com/2012/07/19/adobe-captivate-6-x-widget-google-lms-with-email-reporting/
Suddenly this morning we realised that it is no longer recording information into our google sheets. It was working fine yesterday. The company that we purchased the widget from has closed down, and I cannot find anyone to contact for support.
Any ideas on what might be the issue?
I know this is a very old post so you probably found your solution.
What worked for me...
I changed the way that I create my links.
Before I used...
http://yourwebserver/yourcaptivateprojects/your%20project/index.html
Today I use...
http://yourwebserver/yourcaptivateprojects/your%20project/your%20project.htm
I still finish the project choosing the 'flash' and 'html' option.
I really like the widget; logging results to a Google spreadsheet is very cool. It is too bad that the solution only works with flash installed on the device.
Regards,
Chris
this morning I noticed my Chrome updated to Chrome 22 and that the search in the top right has been removed and can now be accessed with ctrl-f.
I also noticed that ctrl-shift-f is no longer working as expected... (but this is inconsistent)
The global search has been a huge time saver for me, and now sometimes it doesn't work until I've viewed a script at least once.
For example, I have 5 scripts that I know all contain "fn_init"
I search for fn_init and nothing comes up.
I open one of those scripts and then ctrl-shift-f again, and finally get a matching result for just the one file...
Is this working as intended? Am I missing an option or something? My dev tools config options are:
General
Disabled cached
Sources
Show folders checked
Search in content scripts checked
Also: how can I install an older version of Chrome and stop it from updating automatically?
To get an older version of Chrome your best bet is to find a build of Chromium from https://chromium-build.appspot.com/p/chromium/console however if this if for devtools stability you are missing out on a lot of new features and bug fixes.
As for Search across all files it is still there and CTRL-SHIFT-F on Windows and CMD-OPT-F on Mac. See Addy Osmani's post https://plus.google.com/115133653231679625609/posts/e4W2kdrFJY9
If you find issues as bugs, it is better to raise the issue on http://crbug.com/new as it will get direct attention from the engineering team there.