autoConvert does not work well with many modern websites that use technologies like react, vue or angular. It also tends to slow down some websites ocassionally.
autoConvert Select has been designed to work smoothly with modern web technologies. Being request based, it does not impact website performance either. autoConvert Select even converts time zones! It will be the main extension developed going forward.
autoConvert Select is available on both Chrome and Firefox, and may soon come to Android as well.
Currency conversion feature has been removed from autoConvert.
The previous (free) source for currency exchange rates was removed by the provider. I have been unable to find another free source, so the feature had to be removed.
I intend to bring the feature back in the new extension – autoConvert Select at some time in the future.
The old autoConvert extension will be deprecated near the end of 2018.
Unit conversion in autoConvert will continue to function normally as long as you have the extension installed. But there won’t be any new development on the extension.
autoConvert Select is the place to go for that, and more!
See instant conversion of units and times in pasted text
Convert text from other apps using autoConvert Select
Copy the text in the other app (say, from an email in Outlook), click on the autoConvert Select button in Chrome, and paste the text in the text box. autoConvert will instantly convert all units and times found in the text.
Convert more than 6 items from a web page
The limit of 6 conversions at a time does not apply to conversions done using the autoConvert Select window. Copy all the text from a webpage and paste into the text box. All conversions found in the text will be displayed1
Offline conversions of units and times
Google provides a handy converter for units and time zones. autoConvertSelect makes it one better by providing similar functionality even without an internet connection. Like before, open Chrome, open the autoConvert Select window, and type in whatever you want coverted. It’s done, pronto.
Made a minor tweak to the app icon, just enough to marginally differentiate from the now-deprecated autoConvert extension.
AutoConvert Select reads the dates provided with times when converting time zones. As usual, just select the date and time with the time zone, and the conversion appears. When the extension is unable to parse the date, the time zone is converted assuming today’s date.
For the wanderers, the readers, the chefs and bakers, the measuring, tinkering DIYers, and for anyone else who struggles to convert feet to cm, or ºC to ºF, or wonders how many grams is it when the recipe says a cup of sugar in the cake.
With autoConvert Select, just select the text you convert, and the conversion is right there in the corner of the browser. No clicking, no searching. Right there… automagically.
Select a value in metric units, say 16 km, and the conversion will be imperial (10 miles). Select a value in the old, imperial units, say 22ºF, and the conversion will be into metric (-5.6ºC).
Please share your feedback, including suggestions and any bugs you find using this link.
autoConvert Select only converts units. Unlike the older autoConvert for Chrome, it does not convert currencies yet. I am still looking for a free source for currency rates before I can provide currency conversion.
autoConvert Select converts the first six values in a selection. You may have to select multiple times to see more conversion.
autoConvert Select supports all websites – including the newer React based websites that the older extension used to hang on.
Currency conversion in autoConvert seems to have stopped working.
It appears that the (free) API that the extension uses to fetch currency rates was removed. This has broken currency conversion.
I’ll try and look for a new (free) currency rates API tomorrow (Monday, 22 January). If one is available, I’ll update the extension with it. If I can’t find one, I may have to remove currency conversion entirely.
Update: The issue is caused by pages that use a technology called react – it was first developed by Facebook.
Due to the way react works, I’m unable to convert text on parts of web pages that use react. However, on websites which only use react for some parts of the functionality, autoConvert will continue to operate as normal on the rest of it.
Still doesn’t work on Facebook, though 😦
I’ve finally been able to diagnose the source of the problem – the Facebook’s BigPipe pagelets.
While Facebook is still waiting to receive, loading and dynamically populate the pagelet divs, Chrome declares the page loaded, and fires up autoConvert. This results in autoConvert working with nodes that wouldn’t be there when the conversion happens (BigPipe will replace them with actual, delayed content).
When that happens, Chrome/autoConvert/Facebook go in a lockup, and everything hangs.