Chrome 76 arrived a few days ago, by the hand of the default flash lock, simple installation of PWA and dark mode on websites, among others. Despite these benefits, Google has decided to remove the ‘http’ and ‘https’ from the address bar, with a view to making the design of the addresses themselves more minimalist.
If the change does not convince you, you can reverse the situation relatively easily, by modifying some Google Chrome flags. Proceed like this, with how you can do it, quite simply and quickly.
Returning https to your site
As we have indicated, to perform this process you will need to access the Google Chrome flags. In case you still don’t know how to access this section, it won’t hurt to know that you just have to write the following in the address bar.
chrome: // flags
Once you have accessed the flags section, you will see a search engine at the top. You will be warned that some of these functions are experimental and may compromise browser security. In our case, we have been able to test the method, without any problem. Within the search engine mentioned above, we have only to write the following.
Now, we will see the option we have searched for, in which ‘default’ will be marked. The default value of this flag is to be activated, so it will be necessary to deactivate it, for changes to take effect. Without further delay, mark ‘disabled’ as status, and restart the browser.
Once you have done this simple process, you will see the http and https back in your address bar. Changes are applied permanently, unless you reset Google Chrome settings, or change these settings manually again.
The new macOS 10.15 Catalina began its deployment through the Mac App Store two days ago. Since then, there are many users who have started to update a system that arrives for free with interesting news, such as the possibility of using the screen of an iPad as a second monitor with Sidecar or the possibility of using Catalyst applications.
But Catalina, in addition to bringing new things, eliminates support for old things, and with the arrival of version 10.15 of macOS, it says goodbye to support for 32-bit applications. This means that if you have 32-bit apps installed in your current version of macOS and upgrade to Catalina, they will stop working.
Although Apple has implemented a system of alerts that inform you that an application is not optimized for your Mac because it is 32 bits, this message only appears when you run the app, and in Mojave, it only appears once every 30 days. If you want to check the status of all your apps at once, this is the way:
How to verify which of your applications are 32 bits
First click on the Apple logo in the menu bar and select About this Mac. Once the pop-up window appears with the information of your device, click on the System Report button:
Now, in the window that appears look for the Software category among the list of elements that appear in the right column, and within this click on Applications. It takes some time for the list to load, so if nothing appears immediately, you just have to wait a few seconds.
Once the list appears you just have to look at the last column called 64 bits (Intel) and check which applications say “No”. These would be 32-bit applications and therefore will not work in macOS Catalina.
Here are a couple of options, you can expect the developer of that app to update it to be compatible with 64 bits, although considering that Apple warned years ago that Mojave would be the latest version of macOS with support for 32-bit apps, if so far they have not updated it, it is difficult for them to do it at the last minute. Consider that
You can also simply continue using your application as before and not update to Catalina if it is an essential app for you. macOS Mojave will have extended support until September 2021, you still have a couple of years of grace for 32-bit apps.