[Improvement] Why removed call answering/rejecting options with 1.0.7.16 update? Want it back.

Uh, thank you, but I know how. My question is WHY they made this backwards change when it must be more desirable to be able to do such simple actions directly instead of "first this then that". And my request is to put it BACK the way it was, not something "new for the next update".

I perfectly agree with you, I hope that lots of people will vote this proposal so Jolla will make our desire real

If you want it back, you should draw up a vote with equal chances for both, denying a change as well as requesting a change. Then it would be possible to work out whether the interest of the majority is a quick and sure silencing of incoming calls not appropriate right that moment (remember sitting in-between an audience and having forgotten to silence your phone in advance) or allowing for a longer action until the phone is silenced but being able to select the silencing options from a menu within the same step.

I prefer the quick silencing!

@jgr, I'm not saying not to be able to mute the sound. This option was always there before and should be there absolutely. I'm saying to keep the other options directly accessible like it was before this update. And if you want the other alternative to vote on, it's already right here !! And with 15 votes it was apparently enough to compel the developer to spend the time on changing it without possibility to personalize that function, while they (the devs) could've used the time to fix other more interesting issues such as showing the caller number on call log... Bottom line, I never experienced it was difficult or slightly more time-consuming to mute it before since it was the first option in the red menu!

@spacenewt: The difference is, whether you just pull up without even looking onto the display and have muted the phone or whether you have to carefully adjust your pull to exactly the option you want.

Due to the now different behavior, the situation is anew. A poll should be set-up properly if it is about to work out what the majority wants. From the other question the developers may simply have realized that there is a need for improvement. There is no sense in now just casting enough votes to make the developers changing this feature back to the original state -- only to have then the rage going the other way round: "I want .... back!"