Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Launch Chrome.
2. Open https://blog.strongbrew.io/rxjs-best-practices-in-angular/#ascii-marble-diagrams in Chrome for Android
3. Tap menu, then share. Share to some app or clipboard.
4. The url that is shared is an invalid url "https://rxjs-best-practices-in-angular/"

Chrome versions tested:
66.0.3359.126(Stable), 68.0.3420.1(Canary)

OS:
Android 8.1.0

Android Devices:
Pixel 2

Using the per-revision bisect providing the bisect results,
Good Build - 64.0.3264.0 
Bad Build - 64.0.32645.0 

You are looking for a change made after 515684(GOOD), but before 515685(BAD).

CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+/cd0d03a00f2e1d73c1930dec6611aaabee932e37

@tedchoc: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned.

Please navigate to below link for log's and video--
go/chrome-androidlogs/840457

Note: 
1. This issue is not observed in Desktop.
2. This issue is not observed in FireFox mobile version.

Thanks!

This looks like an issue with just this site.

Chrome switched to sharing the canonical URL in the CL mentioned above and it looks like this site isn't formatted correctly:

<link rel="canonical" href="//rxjs-best-practices-in-angular/">

They need to drop one of the leading '/'s.

Admittedly I don't have the context of why the change to canonical url sharing was made, but I do wonder if this can just lead to confusion in general, since it can lead to the user sharing a different url than what they see in their address bar?

Also, not sure how often websites could get their canonical urls wrong, but would there be any value to having Chrome validate the url and fallback to the visual one if it is invalid?

Thanks for looking into this. Cheers

Updating this issue from Buganizer - b/109879787

1. Open Android chrome 
2. Navigate to: https://www.axs.com/events/355164/thrice-tickets?skin=regency&src=AEGLIVE_WREGYSFO030115VEN001 
3. Tap the Chrome overflow menu 
4. Choose share... 
5. Copy to clipboard (or share to any app) 
6. Observed that the shared link will be - https://www.axs.com/events/355164/www.axs.com/events/355164/thrice-tickets 

somogyi@ -- Could you please confirm whether it is the expected behavior or not.

Thanks!

Based on the examples in #c2 and #c5 this is correct behavior.

The canonical URL is the one that should be shared; it's the responsibility of the site to supply a correct and correctly-formed canonical link.