Feedback Report : feedback/#/Report/65538907550

Description:
Data saver should not prevent Twitter's "t.co" redirects from resolving to the real URL.
URL: https://t.co/gk453SYzR9

UI language:
en_US

Version:
61.0.3124.3

Device Model:
Pixel

Device Release:
8.0.0

App Version:
61.0.3124.3

Product Specific Data (whitelisted):
Chrome Variations:  3300134 3313324 
Connection check elapsed (ms): 119
Connection type: WiFi
Data Reduction Proxy Enabled: true
HTTP connection check (Android network stack): CONNECTED
HTTP connection check (Chrome network stack): CONNECTED
HTTPS connection check (Android network stack): CONNECTED
HTTPS connection check (Chrome network stack): CONNECTED
com.google.android.webview: VersionCode:303012500;VersionName:58.0.3029.125


To reproduce:

      1. Open the Twitter mobile app.
      2. Find a Tweet that contains a link to some other article (such as Washington Post, Forward, etc.)
      3. Click on the link.
      4. Before the link fully loads, click the three-dot vertical menu in the upper right hand corner
      5. Click "Open in Browser"

Observed:

       Chrome launches, displaying the content of the destination page but displaying the URL of the redirect page.
It may be that this is not the result of Data Saver so much as a race condition in updating the URL that is displayed in the URL bar when navigating from a Chrome Custom Tab to Chrome proper.

This is something that cannot be reproduced simply by typing the URL in the browser (in both Chrome Dev and Chrome Stable, I observe that it actually does resolve to the forward.com link if I type in the URL directly both with and without Data Saver). I can, however, reproduce the behavior when poking around on Twitter...