If you open links in some Android apps, and you have Chrome enabled as your default web browser, the page might be opened in a 'Chrome Custom Tab.' Instead of starting up the whole app, only a minimal browser UI is shown, with a large close button that takes you right back to the previous app. This feature requires the app open links a certain way, and as such, there have always been some apps that don't support Custom Tabs.

By using a flag that was introduced in Chrome 52, known as #tab-management-experiment-type, it has been possible to force all links from Android apps to open in Custom Tabs. This was especially handy for apps that are no longer maintained. The flag originally had several settings, but over time, that was reduced to two - 'Disabled' (which would turn off all Custom Tabs, but appears to not work) and 'Elderberry' (which forces Custom Tabs for all apps).

Left and center: Chrome 64 (stable); Right: Chrome 65 Beta

It seems to have been removed entirely in Chrome 65, which is currently in beta. In other words, there is no longer a way to force all apps to use Custom Tabs. I was unable to find an explanation for its removal, and Google doesn't officially comment on in-development Chrome features, so your guess for the reason is as good as mine.

Chrome 65 is expected to be released on March 5 (at least on the desktop), so you have a little over a week left to enjoy the flag.