Desktop context menu reorganisation

Desktop context menu reorganisation
+ Reorganising the context menus into better groupings
+ Renaming menu item labels for consistency
+ Removing items that are rarely used and have other access points (e.g. spellchecker submenu, page info)
+ Fix writing redirection UMA metrics collection

BUG=506874
Committed: https://crrev.com/5414139041953f2b558cfb0fdf8a4927a19a3144
Cr-Commit-Position: refs/heads/master@{#351094}

[edwardjung, 2015-09-25 19:34:32]

edwardjung@chromium.org changed reviewers:
+ asvitkine@chromium.org

[edwardjung, 2015-09-25 19:34:32]

edwardjung@chromium.org changed reviewers:
+ asvitkine@chromium.org

[edwardjung, 2015-09-25 19:39:36]

edwardjung@chromium.org changed reviewers:
- asvitkine@chromium.org

[edwardjung, 2015-09-25 19:47:58]

edwardjung@chromium.org changed reviewers:
+ avi@chromium.org, isherman@chromium.org, sky@chromium.org

[edwardjung, 2015-09-25 19:47:59]

Hi, all, please take a look respectively at the following files: 

avi: 
chrome/browser/renderer_context_menu/*
chrome/browser/ui/cocoa/renderer_context_menu/*
chrome/browser/ui/views/renderer_context_menu/*

isherman:
tools/metrics/histograms/histograms.xml

sky:
chrome/chrome_tests.gypi
chrome/chrome_browser.gypi

Thank you.

[sky, 2015-09-25 20:15:57]

sky@chromium.org changed reviewers:
- sky@chromium.org

[sky, 2015-09-25 20:15:58]

*gypi has * as owners, so anyone can review the changes.
-sky

[Ilya Sherman, 2015-09-26 00:19:19]

histograms.xml lgtm

[Avi (use Gerrit), 2015-09-26 02:26:15]

Lots of weird indenting; you might want to "git cl format" it.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
File chrome/browser/renderer_context_menu/render_view_context_menu.cc (right):

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:159: // Used to
track command usage under specific contexts - Specifically Menu
"... specific contexts, specifically menu items..."

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:164: int
context_specific_enum_id;
This order makes it hard to read the list. Do:

const struct UmaEnumCommandIdPair {
  int enum_id;
  int context_specific_enum_id;
  int control_id;
} //...

and _explicitly_ give values for the context_specific_enum_id in the list below.
You can use whatever value you want to mean "ain't none", but please don't rely
on the language to zero-fill.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:264: int
FindUMAEnumValueForCommand(int id, bool use_specific_context_enum) {
This is a magic bool as a parameter that is impossible to grok meaning from. If
you don't want to split this into two functions, make a quick two-valued enum
and use that instead.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:278:
kUmaEnumToControlId[i].context_specific_enum_id > -1) {
How could this ever not be true? In most of the list items above, you only
provide two initializers in the aggregate. In that case, that third value will
be default initialized to 0 (see the C++11 spec, [dcl.init.aggr], §8.5.1
Aggregates, ¶7). And given that all the values that you _do_ give are positive,
how could your clause "kUmaEnumToControlId[i].context_specific_enum_id" ever
_not_ be greater than -1?

Like I said above, make the two IDs the first two members, and explicitly give
all the values explicitly-specified ids. Even the ones you set to -1 or
whatever.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:633: }
Your indenting is wack; please fix.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:699:
ContextMenuContentType::ITEM_GROUP_PRINT)) {
Your indenting is weird; you should indent line 697 and 699. Or let clang-format
handle it.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:767:
IDS_CONTENT_CONTEXT_VIEWFRAMESOURCE);
Are these useful comments? I would say no.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:996: // 'Undo'
and 'Redo' for tText input with no suggestions and no text selected.
typo: tText

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:997: // We make
an exception for OSX as context clicking will select the closest
s/OSX/Mac OS X/ or /OS X/ or /the Mac/

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
File chrome/browser/renderer_context_menu/spelling_menu_observer.cc (right):

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer.cc:85: ?
kMaxSpellingSuggestions : params.dictionary_suggestions.size();
std::min!

(Bad indenting, anyway.)

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
File chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc
(right):

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:268:
// "Add to dictionary", "Ask Google for suggestions",and a separator.
space after a comma

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:271:
EXPECT_EQ(static_cast<size_t>(3), menu()->GetMenuSize());
er, just do 3u

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:316:
EXPECT_EQ(static_cast<size_t>(3), menu()->GetMenuSize());
3u

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:344:
// "Ask Google for suggestions",and a separator.
space after a comma

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:345:
// Possibly more items (not relevant here).
Combine this comment line with the previous one.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:402:
// They should not see "No more Google suggestions" (from SpellingService) or
Who is "they"? Maybe "There should not be xxxx nor xxxx".

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:428:
EXPECT_EQ(static_cast<size_t>(3), menu()->GetMenuSize());
3u

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:439:
EXPECT_LT(static_cast<size_t>(4), menu()->GetMenuSize());
4u

[edwardjung, 2015-09-28 14:11:24]

edwardjung@chromium.org changed reviewers:
+ sky@chromium.org

[edwardjung, 2015-09-28 14:11:26]

> *gypi has * as owners, so anyone can review the changes.
> -sky

Doh, sorry @sky, I wanted you too look at the one line change in:
chrome/browser/ui/views/renderer_context_menu/render_view_context_menu_views.cc

Avi, I've done another pass, apologies for not getting the styling sorted.
Forgot about the git cl format command.

Thanks.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
File chrome/browser/renderer_context_menu/render_view_context_menu.cc (right):

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:159: // Used to
track command usage under specific contexts - Specifically Menu
On 2015/09/26 02:26:15, Avi wrote:
> "... specific contexts, specifically menu items..."

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:164: int
context_specific_enum_id;
On 2015/09/26 02:26:15, Avi wrote:
> This order makes it hard to read the list. Do:
> 
> const struct UmaEnumCommandIdPair {
>   int enum_id;
>   int context_specific_enum_id;
>   int control_id;
> } //...
> 
> and _explicitly_ give values for the context_specific_enum_id in the list
below.
> You can use whatever value you want to mean "ain't none", but please don't
rely
> on the language to zero-fill.

Makes sense, done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:264: int
FindUMAEnumValueForCommand(int id, bool use_specific_context_enum) {
On 2015/09/26 02:26:15, Avi wrote:
> This is a magic bool as a parameter that is impossible to grok meaning from.
If
> you don't want to split this into two functions, make a quick two-valued enum
> and use that instead.

Understood. Changed to use an enum.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:278:
kUmaEnumToControlId[i].context_specific_enum_id > -1) {
Understood. Fixed.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:633: }
On 2015/09/26 02:26:15, Avi wrote:
> Your indenting is wack; please fix.

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:699:
ContextMenuContentType::ITEM_GROUP_PRINT)) {
On 2015/09/26 02:26:15, Avi wrote:
> Your indenting is weird; you should indent line 697 and 699. Or let
clang-format
> handle it.

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:767:
IDS_CONTENT_CONTEXT_VIEWFRAMESOURCE);
On 2015/09/26 02:26:15, Avi wrote:
> Are these useful comments? I would say no.

Removed.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:996: // 'Undo'
and 'Redo' for tText input with no suggestions and no text selected.
On 2015/09/26 02:26:15, Avi wrote:
> typo: tText

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/render_view_context_menu.cc:997: // We make
an exception for OSX as context clicking will select the closest
On 2015/09/26 02:26:15, Avi wrote:
> s/OSX/Mac OS X/ or /OS X/ or /the Mac/

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
File chrome/browser/renderer_context_menu/spelling_menu_observer.cc (right):

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer.cc:85: ?
kMaxSpellingSuggestions : params.dictionary_suggestions.size();
On 2015/09/26 02:26:15, Avi wrote:
> std::min!
> 
> (Bad indenting, anyway.)

Apologies, my poor C++ knowledge is really showing.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
File chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc
(right):

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:268:
// "Add to dictionary", "Ask Google for suggestions",and a separator.
On 2015/09/26 02:26:15, Avi wrote:
> space after a comma

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:271:
EXPECT_EQ(static_cast<size_t>(3), menu()->GetMenuSize());
On 2015/09/26 02:26:15, Avi wrote:
> er, just do 3u

Hadn't realised this. Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:316:
EXPECT_EQ(static_cast<size_t>(3), menu()->GetMenuSize());
On 2015/09/26 02:26:15, Avi wrote:
> 3u

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:344:
// "Ask Google for suggestions",and a separator.
On 2015/09/26 02:26:15, Avi wrote:
> space after a comma

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:345:
// Possibly more items (not relevant here).
On 2015/09/26 02:26:15, Avi wrote:
> Combine this comment line with the previous one.

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:402:
// They should not see "No more Google suggestions" (from SpellingService) or
On 2015/09/26 02:26:15, Avi wrote:
> Who is "they"? Maybe "There should not be xxxx nor xxxx".

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:428:
EXPECT_EQ(static_cast<size_t>(3), menu()->GetMenuSize());
On 2015/09/26 02:26:15, Avi wrote:
> 3u

Done.

https://codereview.chromium.org/1357393002/diff/100001/chrome/browser/rendere...
chrome/browser/renderer_context_menu/spelling_menu_observer_browsertest.cc:439:
EXPECT_LT(static_cast<size_t>(4), menu()->GetMenuSize());
On 2015/09/26 02:26:15, Avi wrote:
> 4u

Done.

[sky, 2015-09-28 15:23:31]

One line change in
chrome/browser/ui/views/renderer_context_menu/render_view_context_menu_views.cc
LGTM

[Avi (use Gerrit), 2015-09-28 15:29:22]

lgtm

👍

[edwardjung, 2015-09-28 16:26:12]

The CQ bit was checked by edwardjung@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-09-28 16:26:24]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1357393002/140001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1357393002/140001

[commit-bot: I haz the power, 2015-09-28 16:35:58]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-28 16:35:59]

Dry run: This issue passed the CQ dry run.

[edwardjung, 2015-09-28 18:49:27]

The CQ bit was checked by edwardjung@chromium.org

[edwardjung, 2015-09-28 18:49:27]

The patchset sent to the CQ was uploaded after l-g-t-m from
isherman@chromium.org
Link to the patchset: https://codereview.chromium.org/1357393002/#ps140001
(title: " ")

[commit-bot: I haz the power, 2015-09-28 18:52:13]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1357393002/140001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1357393002/140001

[commit-bot: I haz the power, 2015-09-28 19:15:20]

Committed patchset #8 (id:140001)

[commit-bot: I haz the power, 2015-09-28 19:16:35]

Patchset 8 (id:??) landed as
https://crrev.com/5414139041953f2b558cfb0fdf8a4927a19a3144
Cr-Commit-Position: refs/heads/master@{#351094}

[iakaox, 2015-12-14 10:58:24]

+ Removing items that are rarely used and have other access points (e.g.
spellchecker submenu, page info)

This doesn't make sense as a lot of users are already complaining. Users that
write in more than one language would actually used this feature thoroughly and
now are impeded from using the spell-checker.

How can we go about on rolling back on this feature?

[ggpanta, 2015-12-15 11:35:15]

On 2015/12/14 10:58:24, iakaox wrote:
> + Removing items that are rarely used and have other access points (e.g.
> spellchecker submenu, page info)
> 
> This doesn't make sense as a lot of users are already complaining. Users that
> write in more than one language would actually used this feature thoroughly
and
> now are impeded from using the spell-checker.
> 
> How can we go about on rolling back on this feature?

The spellchecker submenu is rarely used only by users that speak a single
language, I understand that people using only English would not find it useful
but for the rest of us that do 3+ we really need it. Chrome has been a nice
browser but having to type stuff outside the browser in order to paste them in
it makes it kinda useless. 
I propose that this change should be rethinked fast unless Google would like us
all to start using a single language (something tells me its not going to happen
any time soon).

[edwardjung, 2015-12-15 12:00:09]

Do you want to add your comment to the bug that's open:
https://code.google.com/p/chromium/issues/detail?id=544234

We'll review all the comments.

[siteadmin, 2016-01-08 08:12:25]

Please re-add "right-click change spell-check language option", or provide a
means to add it manually, or a mean to roll-back chrome user version and
permanently disable chrome self-update feature to prevent future function
breakage.

Thanks

[cpzhispania, 2016-01-18 16:39:22]

On 2016/01/08 08:12:25, siteadmin wrote:
> Please re-add "right-click change spell-check language option", or provide a
> means to add it manually, or a mean to roll-back chrome user version and
> permanently disable chrome self-update feature to prevent future function
> breakage.
> 
> Thanks

Chiming in on this. Looking to roll-back to a version that has the right-click
spell-checker lang switch. Chrome it's a pain to use without it, I use this
feature on a daily basis. Are you including mobile and tablet data sets on the
statistics you based this information on by any chance? Otherwise I can't think
of a reason how this feature was marked as under-used.

Please bring back this functionality.

[paulo.s.matos, 2016-02-11 11:30:25]

On 2016/01/18 16:39:22, cpzhispania wrote:
> On 2016/01/08 08:12:25, siteadmin wrote:
> > Please re-add "right-click change spell-check language option", or provide a
> > means to add it manually, or a mean to roll-back chrome user version and
> > permanently disable chrome self-update feature to prevent future function
> > breakage.
> > 
> > Thanks
> 
> Chiming in on this. Looking to roll-back to a version that has the right-click
> spell-checker lang switch. Chrome it's a pain to use without it, I use this
> feature on a daily basis. Are you including mobile and tablet data sets on the
> statistics you based this information on by any chance? Otherwise I can't
think
> of a reason how this feature was marked as under-used.
> 
> Please bring back this functionality.

Please, rollback this change! Por favor, anulem esta alteração! Por favor,
anulen este cambio! Per piacere, annullate questo cambiamento! S'il vous plaît,
annulez ce changement! (English/Portuguese/Spanish/Italian/French typer)

Same here, check it:
https://productforums.google.com/forum/#!msg/chrome/7T2ztGVpJBk/i6m7bVdmBQAJ

[jean-marie.duno, 2016-03-02 17:25:41]

On 2016/02/11 11:30:25, paulo.s.matos wrote:
> On 2016/01/18 16:39:22, cpzhispania wrote:
> > On 2016/01/08 08:12:25, siteadmin wrote:
> > > Please re-add "right-click change spell-check language option", or provide
a
> > > means to add it manually, or a mean to roll-back chrome user version and
> > > permanently disable chrome self-update feature to prevent future function
> > > breakage.
> > > 
> > > Thanks
> > 
> > Chiming in on this. Looking to roll-back to a version that has the
right-click
> > spell-checker lang switch. Chrome it's a pain to use without it, I use this
> > feature on a daily basis. Are you including mobile and tablet data sets on
the
> > statistics you based this information on by any chance? Otherwise I can't
> think
> > of a reason how this feature was marked as under-used.
> > 
> > Please bring back this functionality.
> 
> Please, rollback this change! Por favor, anulem esta alteração! Por favor,
> anulen este cambio! Per piacere, annullate questo cambiamento! S'il vous
plaît,
> annulez ce changement! (English/Portuguese/Spanish/Italian/French typer)
> 
> Same here, check it:
> https://productforums.google.com/forum/#!msg/chrome/7T2ztGVpJBk/i6m7bVdmBQAJ

It is used !
On my company we are all using local and english language all the day.
The language switch is used many time per days !

Please roll back this change.

[serge, 2016-03-09 08:44:11]

On 2016/03/02 17:25:41, jean-marie.duno wrote:
> On 2016/02/11 11:30:25, paulo.s.matos wrote:
> > On 2016/01/18 16:39:22, cpzhispania wrote:
> > > On 2016/01/08 08:12:25, siteadmin wrote:
> > > > Please re-add "right-click change spell-check language option", or
provide
> a
> > > > means to add it manually, or a mean to roll-back chrome user version and
> > > > permanently disable chrome self-update feature to prevent future
function
> > > > breakage.
> > > > 
> > > > Thanks
> > > 
> > > Chiming in on this. Looking to roll-back to a version that has the
> right-click
> > > spell-checker lang switch. Chrome it's a pain to use without it, I use
this
> > > feature on a daily basis. Are you including mobile and tablet data sets on
> the
> > > statistics you based this information on by any chance? Otherwise I can't
> > think
> > > of a reason how this feature was marked as under-used.
> > > 
> > > Please bring back this functionality.
> > 
> > Please, rollback this change! Por favor, anulem esta alteração! Por favor,
> > anulen este cambio! Per piacere, annullate questo cambiamento! S'il vous
> plaît,
> > annulez ce changement! (English/Portuguese/Spanish/Italian/French typer)
> > 
> > Same here, check it:
> > https://productforums.google.com/forum/#!msg/chrome/7T2ztGVpJBk/i6m7bVdmBQAJ
> 
> It is used !
> On my company we are all using local and english language all the day.
> The language switch is used many time per days !
> 
> Please roll back this change.

Please roll-back it!

How is possible automatically determine what language I need to write? Say here
I write "Presentation"... Just this word. Should I mean English word (OK) or
maybe French (NOK, because of accent "Présentation")? Only I know what language
I would like to use, what a stupid movie from Google Stuff members!

[serge, 2016-03-09 08:48:05]

On 2016/03/09 08:44:11, serge wrote:
> On 2016/03/02 17:25:41, jean-marie.duno wrote:
> > On 2016/02/11 11:30:25, paulo.s.matos wrote:
> > > On 2016/01/18 16:39:22, cpzhispania wrote:
> > > > On 2016/01/08 08:12:25, siteadmin wrote:
> > > > > Please re-add "right-click change spell-check language option", or
> provide
> > a
> > > > > means to add it manually, or a mean to roll-back chrome user version
and
> > > > > permanently disable chrome self-update feature to prevent future
> function
> > > > > breakage.
> > > > > 
> > > > > Thanks
> > > > 
> > > > Chiming in on this. Looking to roll-back to a version that has the
> > right-click
> > > > spell-checker lang switch. Chrome it's a pain to use without it, I use
> this
> > > > feature on a daily basis. Are you including mobile and tablet data sets
on
> > the
> > > > statistics you based this information on by any chance? Otherwise I
can't
> > > think
> > > > of a reason how this feature was marked as under-used.
> > > > 
> > > > Please bring back this functionality.
> > > 
> > > Please, rollback this change! Por favor, anulem esta alteração! Por favor,
> > > anulen este cambio! Per piacere, annullate questo cambiamento! S'il vous
> > plaît,
> > > annulez ce changement! (English/Portuguese/Spanish/Italian/French typer)
> > > 
> > > Same here, check it:
> > >
https://productforums.google.com/forum/#!msg/chrome/7T2ztGVpJBk/i6m7bVdmBQAJ
> > 
> > It is used !
> > On my company we are all using local and english language all the day.
> > The language switch is used many time per days !
> > 
> > Please roll back this change.
> 
> Please roll-back it!
> 
> How is possible automatically determine what language I need to write? Say
here
> I write "Presentation"... Just this word. Should I mean English word (OK) or
> maybe French (NOK, because of accent "Présentation")? Only I know what
language
> I would like to use, what a stupid movie from Google Stuff members!

I write "Presentation" as a texbox field. I need that this word be correct in
French... 
But stupid Chrome thinks that I wrote a English word, and does not underline
it...
I am not sure where and what kind of accent I should use in this French word, so
I have any way to test it, I should open Microsoft word, select text, select
French, and only then it underlines me the error... Before it worked in Chrome,
now it does not!

Bad guys !