UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0

Steps to reproduce the problem:
1. Have too many command line switches in Chrome shortcut target to add --ssl-version-min=
2. Open chrome in new incognito window from task-bar 
3. Open chrome from a link in third party application

What is the expected behavior?
Chrome Minimum TLS enforced system wide 

What went wrong?
ssl-version-min broken! Min Tls can only be enforced from a shortcut and is broken if you load a link from a third party application like Thunderbird or Outlook express. This is unacceptable for user security.

Did this work before? N/A 

Chrome version: 71.0.3551.0  Channel: stable
OS Version: Windows 7 x64 SP1
Flash Version: none

Depreciated ciphers and TLS session tickets are the weakest link in the TLS chain. Disabling them is critical to ensure safe and secure browsing. Command line switches are limited to a max of 269 bytes in windows. This is totally unacceptable, and forces users to compromise on security and preferences, and unnecessary and time wasting efforts, like loading chromium from command prompt. On top of that, these switches are not executed when loading web links outside the command line. This is completely illogical. 

Solution: Add Min TLS, Cipher Selection & Priority, and option to disable TLS session tickets in chrome://flags/ & even better, under privacy & security settings. This will also encourage users become more educated in security critical TLS functionality. 

Read more: https://blog.filippo.io/we-need-to-talk-about-session-tickets/

Thanks!