hasPermanentMenuKey should return false when menu action is mapped to long press button

[moneytoo]

Sorry for bugging you here but as there's no M snapshot release for klte and I have no logcat, so I write here instead of CM tracker.

With stock firmware, there's no permanent menu key but the task button retains such functionality when long pressing it.

With CyanogenMod there's no such functionality by default so I have to set it in menu to open menu when long pressing the task button. This however changes the return value of WindowManager.hasMenuKeyEnabled() and therefore ViewConfiguration.hasPermanentMenuKey() to true.

In my case, I want to the primarily used software menu in apps such as Chrome or Firefox (which test hasPermanentMenuKey()) while having menu press accessible for some legacy apps (Xabber and many more).
Because Galaxy S5 with stock firmware passed Google Android Compatibility tests, I guess that it's correct to return false even when menu action is mapped to long press.

[ahmedsolima]

As

[2favn]

Ok