UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1.url = chrome://flags 
2. View flags with "Default" designation
3. Explain to someone what "default" actually is

What is the expected behavior?
Some sort of notation or GUI effect that shows the user what "default" means.

What went wrong?
I'm going to pick on WebRTC Echo Canceller 3 because it's towards the top of the list, but this applies to all flags that have a drop down.

If you look at WebRTC Echo Canceller 3, you're presented with "Default", "Enabled" or "Disabled".  Since there isn't a note that says "XYZ is Default", a person is left trying to guess whether the default is "Enabled", or "Disabled".  In the case of "Restrict Native Client GDB-based debugging by pattern", if it gets changed from its default setting, there is zero way to know what the actual default setting was to put it back.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 10.0
Flash Version: 

Thinking about it, the flags with "Default", are either on or off to begin with, so why even bother with a "default" setting?  It should display whether it is enabled (default) or disabled (not default) like the other flags that have been switched over to on-off values.  These make sense.

For the flags that have different options, such as Touch Events API which is "Automatic", there needs to be some sort of indicator that "Automatic" is the default setting, and Enable or Disable are optional switches.

Since the switch to Material and a few other issues in the queue pointing to the horrible UI, it's gotten a lot better, but it's still not quite there yet.