UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.25 Safari/537.36

Steps to reproduce the problem:
1. chrome://flags/

What is the expected behavior?

What went wrong?
Mention what non-default items will look like on chrome://flags/:

"Experiments
68.0.3440.17
WARNING: EXPERIMENTAL FEATURES AHEAD! By enabling these features, you
could lose browser data or compromise your security or privacy. Enabled
features apply to all users of this browser."

Add: "A blue dot to the left of an item will appear next to items not in
their default state".

Else one cannot guess their state.

Even worse, some items have
Enabled, Disabled
and some
Enabled, Disabled, Default
choices.

And on some items, when you change them from Enabled to Disabled, and
restart, the blue dot's mouseover says "Experiment Enabled'!!

Anyway before restarting the blue dot has no mouseover action.

OK maybe indeed Disabling some items is considered an experimental
action... so Disabling = Enabling... what a mess.

Also on chrome://flags mention where to find the list of e.g., 
--use-gl=osmesa invocation flags/options in use/available.

Did this work before? N/A 

Chrome version: 68.0.3440.25  Channel: n/a
OS Version: 
Flash Version: