Alex, wdyt?  Can we chop off the ...?  Or is there a reason to keep it?

I defer to hwi@ and srahim@ 

The rationale has traditionally been that we keep a "..." for things that require an extra step (vs. things that happen immediately on release). You can see that in the Wrench menu, for example.

Ah, that makes sense.  Thanks for the explanation!

As long as there's a reason for this (which it's now clear there is), I'm fine with it.  hwi@, any thoughts?  mpearson@, does this seem reasonable, or still strike you as odd?

> mpearson@, does this seem reasonable, or still strike you as odd?
I understand the reasoning now.  Nonetheless, I still think it looks odd.  (It's not a practice I recall seeing elsewhere on the web or in apps.)  But, it's not my decision.

1. For this bug: I recommend we keep "..." for now to maintain the consistency with today's style with the reasoning per c3. 

2. Long term: srahim@, this might be in your radar already for your ongoing audit. Could this be added to your audit for future direction for buttons and also for menus if it makes sense to change the style? 

Thanks!

Thanks for your attention to detail! Both Mac and Win OS guidelines do indeed recommend using an ellipsis in this scenario. Because Chrome UI text follows the OS-level guidelines, Alex & Hwi are correct.

This style may look odd to you b/c we've stopped doing it in Google products, per Google UX guidelines.
(https://material.googleplex.com/style/writing.html#writing-capitalization-punctuation)

I'll add to my audit per c#6, but a quick review of current usage makes me suspect Chrome on Mac and Win is already handling it correctly. I found one ... on Android that we should remove to maintain consistency w/Google style (Share...).

Thanks for the explanation.