Obsolete
Status Update
Comments
pa...@gmail.com <pa...@gmail.com> #2
This feature would greatly improve the usability of text fields.
dd...@gmail.com <dd...@gmail.com> #3
[Comment deleted]
je...@gmail.com <je...@gmail.com> #5
Looks like I just lost lots of data
ia...@gmail.com <ia...@gmail.com> #6
[Comment deleted]
go...@gmail.com <go...@gmail.com> #7
This seems pretty simple.
sa...@gmail.com <sa...@gmail.com> #8
I can't believe such a basic feature was omitted! It's such an odd thing to overlook, doesn't everyone use undo regularly?
Please consider adding this essential feature asap.
Please consider adding this essential feature asap.
sa...@gmail.com <sa...@gmail.com> #9
[Comment deleted]
sa...@gmail.com <sa...@gmail.com> #10
[Comment deleted]
sm...@gmail.com <sm...@gmail.com> #11
[Comment deleted]
an...@gmail.com <an...@gmail.com> #12
This is a must. Unbelievable in 2010! This should be a global function (e.g. like in Palm OS).
go...@gmail.com <go...@gmail.com> #13
As far as I can tell, 2.2 doesn't have undo either. Honestly, I would hope this could be implemented as a bug-fix instead of an enhancement, and that way older OS could be updated with it as well.
Maybe initiated as a market app such as was done with Google Maps navigation?
Maybe initiated as a market app such as was done with Google Maps navigation?
ma...@gmail.com <ma...@gmail.com> #14
This is ridiculous. No undo function in an OS in 2010?
be...@gmail.com <be...@gmail.com> #15
undo is good...
cr...@gmail.com <cr...@gmail.com> #16
Yup, undo is essential. If they're going to develop so many office and memo/tasks apps, then they should have expected people to really miss the undo button. It can't really be that hard to implement stack data structure for individual text editing programs right?
pr...@gmail.com <pr...@gmail.com> #17
Seriously, wtf... no undo? I just got my first Android phone... can't believe there is no undo! My WinMo 5 phone even did this.
ia...@gmail.com <ia...@gmail.com> #18
now.
po...@gmail.com <po...@gmail.com> #19
There's a bunch of quirky things to Android, but this is the top! On my HTC G2 with qwerty, the Delete button is right above the Enter button. I must lose a huge chunky text message once a day, probably more!
gp...@gmail.com <gp...@gmail.com> #20
The way Android handels text editing DRIVES ME CRAZY. It's not just no UNDO. CUT, COPY, PASTE and text selection is also needing some better methods. On my "old" palm: I could swipe text with my finger for selection, then using the keyboard do CUT, COPY, PASTE or UNDO. No special modes or screens, start of text selection, end of text selection. It was much simpler. I can't believe that this is only rated at Medium priority. I often want to throw the phone away for this issue alone. I've lost some important text that I can't get back. Highly Frustrating!!
ma...@gmail.com <ma...@gmail.com> #21
On Comment 19: If you have a physical keyboard, the combination menu+z does work as undo. At least on my Motorola Milestone. And AFAIK Motorola has not customized the OS at all.
ec...@gmail.com <ec...@gmail.com> #22
Zzzzz
On my motorola droid (which is the US version of the milestone) I'm running bugless beast (it's an AOSP froyo rom with gingerbread bits) menu z just prints zs and opens the menu. :(
You're just holding down the menu key like a modifier right?
On my motorola droid (which is the US version of the milestone) I'm running bugless beast (it's an AOSP froyo rom with gingerbread bits) menu z just prints zs and opens the menu. :(
You're just holding down the menu key like a modifier right?
ha...@gmail.com <ha...@gmail.com> #23
@21:
This also depends on what keyboard you're using. I have a D1, and I know the stock keyboard & the latest version of swype have the copy/cut/paste shortcuts, while SwiftKey does not.
This also depends on what keyboard you're using. I have a D1, and I know the stock keyboard & the latest version of swype have the copy/cut/paste shortcuts, while SwiftKey does not.
go...@gmail.com <go...@gmail.com> #24
@22, as far as I can tell on-screen keyboards can't do cut and paste. I have a nexus S and can't find any way of doing it (you can't even hit menu and Z at the same time bc the menu covers Z.
Nexus S is as stock and new android as it gets.
Nexus S is as stock and new android as it gets.
go...@gmail.com <go...@gmail.com> #25
that last comment was referring to Undo, my bad.
vi...@gmail.com <vi...@gmail.com> #26
[Comment deleted]
ha...@gmail.com <ha...@gmail.com> #27
Sorry I was a little vague;
To clarify, I was referring to those shortcuts while using one of the aforementioned keyboard interfaces, but actually pressing the commands on a hardware keyboard. As you mentioned, these shortcuts will not work with any software keyboard. Furthermore, there is no Undo function to be found any OS, any keyboard.
To clarify, I was referring to those shortcuts while using one of the aforementioned keyboard interfaces, but actually pressing the commands on a hardware keyboard. As you mentioned, these shortcuts will not work with any software keyboard. Furthermore, there is no Undo function to be found any OS, any keyboard.
ma...@gmail.com <ma...@gmail.com> #28
Sorry, my mistake (#20). I remembered wrong. Menu+X, Menu+C and Menu+V work, but Menu+Z does nothing. So no undo on the Milestone either.
ja...@gmail.com <ja...@gmail.com> #29
Blahzz
th...@gmail.com <th...@gmail.com> #30
This just screwed me big time. I will switch OS's if this is not fixed within a few months. It has gone on way too long and is totally amateur for computers not to have this integral feature that has been around for so long. This is among the most important features for a computer to have and as a business user I am unable to trust a machine to treat my data properly without it. Fix it tonight please, this is crap.
ja...@gmail.com <ja...@gmail.com> #31
MAJOR fail. Just switched from Windows Mobile and can't believe all the features I've lost, but this one is the most glaring.
bu...@gmail.com <bu...@gmail.com> #32
Perhaps the Android development team should volunteer to cease using undo in their development environments until this one is fixed?
"Medium Defect"? Really?
What's missing here? Is it a defect in the API that the soft-keyboards must use, or has every single soft-keyboard developer just overlooked this?
If it's a more fundamental problem, could we have an outline of the steps to fix? If Menu+z works with some hardware keyboards, I'm guessing there's some code already buried there somewhere?
Tim.
"Medium Defect"? Really?
What's missing here? Is it a defect in the API that the soft-keyboards must use, or has every single soft-keyboard developer just overlooked this?
If it's a more fundamental problem, could we have an outline of the steps to fix? If Menu+z works with some hardware keyboards, I'm guessing there's some code already buried there somewhere?
Tim.
ec...@gmail.com <ec...@gmail.com> #33
Menu + Z doesn't work ever.
My guess without looking at the code, but from working on other undo codes:
We need:
*An undo queue that tracks all changes to text and breaks them down into useful chunks
*UI elements and hotkeys that tell the undo queue how many change chunks to pop.
*Text editing code that checks the validity of popped chunks and applies them to the text
*Since this is at the OS level we probably need code to decide when the undo queue is no longer valid (cause the user has moved to a new app or submitted the form or something) and discard it. It should probably tend toward keeping code than destorying it.
My guess without looking at the code, but from working on other undo codes:
We need:
*An undo queue that tracks all changes to text and breaks them down into useful chunks
*UI elements and hotkeys that tell the undo queue how many change chunks to pop.
*Text editing code that checks the validity of popped chunks and applies them to the text
*Since this is at the OS level we probably need code to decide when the undo queue is no longer valid (cause the user has moved to a new app or submitted the form or something) and discard it. It should probably tend toward keeping code than destorying it.
JD...@Bravo.name <JD...@Bravo.name> #34
Remember that it isn't just *text editing* that needs to be able to be undone. For instance, I was sorting some data in a spreadsheet the other day and accidentally sorted one column without its neighboring ones included; rendered the entire sheet invalid as the data were essentially now "scrambled." I had to discard the whole spreadsheet and start all over from scratch—which one simple Undo [Sort] would have alleviated.
ec...@gmail.com <ec...@gmail.com> #35
J...@Bravo.name,
I think you may need to file a new bug report for that one. That kind of content-aware app-specific undo isn't provided exclusively by the OS. I've seen some apps that have similar undo functionality already. You should take undoing sort up with the developer of your app.
Perhaps more importantly, from the OP, this is a bug about undoing typing. It's probably a step in the right direction for other undoing, but keeping this bug specific and discrete will make sure it gets done sooner.
I think you may need to file a new bug report for that one. That kind of content-aware app-specific undo isn't provided exclusively by the OS. I've seen some apps that have similar undo functionality already. You should take undoing sort up with the developer of your app.
Perhaps more importantly, from the OP, this is a bug about undoing typing. It's probably a step in the right direction for other undoing, but keeping this bug specific and discrete will make sure it gets done sooner.
fa...@gmail.com <fa...@gmail.com> #36
It should be there for all android versions
uk...@gmail.com <uk...@gmail.com> #37
More votes for this to be above 'medium' prio... More like 'immediate' or what ever your ticketing system uses for most urgent.
Spreadsheets and other applications are probably a concern for 3rd party developers, so I won't be nagging about those.
However the text input control and other stock android UI controls where applicable should get this feature as soon as possible.
Also standardizing menu+z as the convention would be something good to add to UI developer guidelines (if you have a such thing) for those before mentioned 3rd party developers.
Thank you. I've been Android user for 5 days now. It has a lot of potential. Keep up the good work.
Spreadsheets and other applications are probably a concern for 3rd party developers, so I won't be nagging about those.
However the text input control and other stock android UI controls where applicable should get this feature as soon as possible.
Also standardizing menu+z as the convention would be something good to add to UI developer guidelines (if you have a such thing) for those before mentioned 3rd party developers.
Thank you. I've been Android user for 5 days now. It has a lot of potential. Keep up the good work.
gf...@gmail.com <gf...@gmail.com> #38
I am glad its been well over year and there doesn't seem to be any progress or resolution. i want undo maan.
ch...@gmail.com <ch...@gmail.com> #39
On Droid 1 with slide out keyboard: Alt-P to get a zero is treacherous without undo with the delete key right next door. At least once a day, I slip and Alt-delete an entire line of text.
Specifically googled this last year and was shocked to find there's no undo for typing.
Specifically googled this last year and was shocked to find there's no undo for typing.
er...@gmail.com <er...@gmail.com> #40
In the hope that the more valid comments we place, the more likely it is that we get an 'Undo' in the feature, I would like to join the request for an undo command in the edit box.
Too many times, I have 'pasted' a value , in stead of starting the mark . I always have to manually erase the pasted data.
An undo would greatly ease the 'typing' experience.
Too many times, I have 'pasted' a value , in stead of starting the mark . I always have to manually erase the pasted data.
An undo would greatly ease the 'typing' experience.
xi...@xiao-yu.com <xi...@xiao-yu.com> #41
I would say that it wouldn't be such a big issue if alt-del weren't extremely easy to press by mistake on hard keyboards. The alt is the outer most key on the Milestone and the backspace is the second most often used key besides the space because the keyboard isn't so well designed (no separate keys on the bezel). Either make alt-del erase everything only on the condition that they are pressed simultaneously (not alt, then del) or add undo
le...@gmail.com <le...@gmail.com> #42
very basic requirement considering the UI doesn't have much control over too much accidental deletions.
da...@gmail.com <da...@gmail.com> #43
I will come back to WP7!!!! Bye Android - you're suck.
na...@gmail.com <na...@gmail.com> #44
I agree with comment #40 - this is only a big issue because it's so easy to press alt-del and erase the whole line. It's like this on my Droid. Do newer phones with QWERTY keypads have the same issue?
xi...@xiao-yu.com <xi...@xiao-yu.com> #45
#40 is definitely compounded by the fact that on the milestone/droid, numbers are not distinct keys and need alt. This makes the alt usage very frequent and alt-del very frequent and frustrating
[Deleted User] <[Deleted User]> #46
I have a Backflip which has a physical keyboard. I've never hit alt-backspace (delete) I can see how it would be frustrating but I guess I've been lucky. But an undo feature would be great to have.
da...@gmail.com <da...@gmail.com> #47
Undo is absolutely necessary, not just for text but for as many things as possible, just like in any modern OS in computers.
ke...@gmail.com <ke...@gmail.com> #48
So yeah I'd like to throw in my vote and comment for adding undo. Is there really no work being done on this, or it just not being tracked here. Surely the Android team must recognize this as a serious omission...
dn...@gmail.com <dn...@gmail.com> #49
. . Comming from an Touch Pro 2 (Windows Mobile with full qwerty, modifier keys and arrows keys) I find this lack of "ctrl+c", "ctrl+v", "ctrl+x" and "ctrl+z" (or command, if you're into mac) disgusting. Also, most of the screens doesn't have a "cancel" button. Say you started to edit a field and changed your mind about the changes. There is no way of canceling the changes and getting the original value back into the input.
. . The lack of these features is outrageous.
. . The lack of these features is outrageous.
we...@googlemail.com <we...@googlemail.com> #50
undo + cancel , please
see also issue 36923961
see also
ti...@gmail.com <ti...@gmail.com> #51
This whole discussion is making me think about NOT buying an Android enabled device. I know the iPhone can undo things easily, how come this is not a built-in Android function? And why it's Defunct and Medium???????
ca...@gmail.com <ca...@gmail.com> #52
could it be possible to implement an undo on the htc keyboard at least? i found it's very used
al...@gmail.com <al...@gmail.com> #53
@ tibya
I have decided to jump ship and go to iPhone with my next purchase. I am trying to steer others away from Android when I can. It's just a huge mess.
I have decided to jump ship and go to iPhone with my next purchase. I am trying to steer others away from Android when I can. It's just a huge mess.
wr...@gmail.com <wr...@gmail.com> #54
@tibya and @allopatr
I also advise my friends not to buy android phones.
I don't think it is just mature enough at the moment for normal users.
Although i personally still use it. Just bought Galaxy S 2 a week ago.
I also advise my friends not to buy android phones.
I don't think it is just mature enough at the moment for normal users.
Although i personally still use it. Just bought Galaxy S 2 a week ago.
gr...@gmail.com <gr...@gmail.com> #55
Please add undo feature(s).
gf...@gmail.com <gf...@gmail.com> #56
Not a single reply or statement to this by a developer in over 18 months. Same for issue 36923961 , whilst lack of undo keeps being frustrating.
I guess, it is time to recognize that google just won't give us undo. In a rapidly growing market, shiny new bells and whistles more easily translate to sales than fixing a basic usability flaw.
I guess, it is time to recognize that google just won't give us undo. In a rapidly growing market, shiny new bells and whistles more easily translate to sales than fixing a basic usability flaw.
ac...@gmail.com <ac...@gmail.com> #57
This is absolutely unacceptable. 'Undo' and several other basic functionality features--every developer knows which ones I am talking about--should be included in Android's standard keyboard. This is the single, most important update we need. Please, take us seriously!
su...@sushi3.com <su...@sushi3.com> #58
The real bummer here is that people don't even know that this page exists. EVERYONE I know with an Android phone has had an issue with the lack of undo. But NONE of them had even heard of this page.
If we can get everyone to STAR this issue, so that it's significantly more than 100+ strong, I'm sure Google will at least consider it. As it is now, it looks like about 200 people are having the issue.
I'm speculating here, but implementing undo would take a long time to code (as opposed to some other frustrating bugs that would probably take a day to fix); otherwise the custom ROM people would have implemented it already. It's understandably unreasonable for Google to implement this "standard feature" for only 200 people.
If we can get everyone to STAR this issue, so that it's significantly more than 100+ strong, I'm sure Google will at least consider it. As it is now, it looks like about 200 people are having the issue.
I'm speculating here, but implementing undo would take a long time to code (as opposed to some other frustrating bugs that would probably take a day to fix); otherwise the custom ROM people would have implemented it already. It's understandably unreasonable for Google to implement this "standard feature" for only 200 people.
vi...@gmail.com <vi...@gmail.com> #59
[Comment deleted]
vi...@gmail.com <vi...@gmail.com> #60
When I posted this bug, I thought that in no time this would reach one of the top 5, and will soon be fixed. Unfortunately, even after 1 year 8 months, it has gathered only 120 stars and thus, has not been even reviewed by any developer. Pretty sure every user wants this fixed.
bj...@gmail.com <bj...@gmail.com> #61
Ok, I spread this on my twitter and my facebook now. Feel free to retweet: http://mobile.twitter.com/svanstroll/status/123702799153364992
If somebody likes to create a facebook page, we have ourselves an instant campain! :)
If somebody likes to create a facebook page, we have ourselves an instant campain! :)
ma...@gmail.com <ma...@gmail.com> #62
Android is the best mobile SO... just make it perfect!
ka...@gmail.com <ka...@gmail.com> #63
An undo feature would be very helpful
ed...@gmail.com <ed...@gmail.com> #64
Google is going to unveil the Ice Cream Sandwich release in a few hours:
http://www.youtube.com/android
If their are listening to users they will probably implement this feature and many of the most starred ones in this issue tracker (you know this is not the most requested feature)
If their are listening to users they will probably implement this feature and many of the most starred ones in this issue tracker (you know this is not the most requested feature)
bj...@gmail.com <bj...@gmail.com> #65
I just tested the new Xperia Mini Pro, and the IME in that one deleted a LOT of text really quickly if you keep the backspace button pressed. I've only used it for a couple of days, and already swore at least four times because of this, and the lack of undo to get my text back. :P
ma...@gmail.com <ma...@gmail.com> #66
Tablets are not phone... undo feature is ESSENTIAL for taking live notes, also many tablets now take advantage of hardware keyboards (like asus transformer), so CTRL+Z must be a viable option like CTRL+C/V for copy paste. At least ONE text buffer is a bare minimum, i would prefer infinite undo positions depending on memory available. But when you have a huge text, and accidently you block-select an entire paragraph then overwrite the text with a single keystroke, you would trow the whole tablet out of the window!!! No way to recover from the mistake... it's absurd.
ma...@gmail.com <ma...@gmail.com> #67
What about an "undo" button on software keyboard like in iPad ?
Also, this could be invoked using Ctrl+Backspace or other key combination for those having a phisical keyboard connected to the device.
Also, this could be invoked using Ctrl+Backspace or other key combination for those having a phisical keyboard connected to the device.
ti...@gmail.com <ti...@gmail.com> #68
This request seems to be Defunct...
If you've starred this, please star this too, since it's marked as a "Medium Enhancement":
Issue 36923961 : Undo
http://code.google.com/p/android/issues/detail?id=13329
If you've starred this, please star this too, since it's marked as a "Medium Enhancement":
md...@gmail.com <md...@gmail.com> #69
Undo now!!!!!!!!!!!!!!!
st...@gmail.com <st...@gmail.com> #70
Please add UNDO/REDO functionality. Thank you, devs.
we...@gmail.com <we...@gmail.com> #71
A.I.type keyboard includes UNDO, but this should still be a system wide feature. I make mistakes!
ke...@gmail.com <ke...@gmail.com> #72
Do I really need to add that android needs to add an undo/redo function. I just picked up a freebie tablet, 6 hours ago... Lucky me. I already have an ipad, which i use a lot for qork... really lucky me. The delete button on the touch keyboard stuck (wtf!? - this has happened a couple of times now) And deleted most of the text in a fairly long email. I then fund no undo (nw annoyed)
.... while yuor at it a decent spell check/autocrrect wouldnt hurt . Im already sick of correcting my hamfigured typing.
Right niw theres niw way im using this to replace my ipad
.... while yuor at it a decent spell check/autocrrect wouldnt hurt . Im already sick of correcting my hamfigured typing.
Right niw theres niw way im using this to replace my ipad
ry...@gmail.com <ry...@gmail.com> #73
Please, please, please.
to...@gmail.com <to...@gmail.com> #74
Really major flaw for otherwise great OS.
bo...@gmail.com <bo...@gmail.com> #75
google is great except for
1) no undo
2) android gmail having only VERY basic features
3) Outlook sync issues because of Google arrogance that are killing my data - have to go back to symbian :(
1) no undo
2) android gmail having only VERY basic features
3) Outlook sync issues because of Google arrogance that are killing my data - have to go back to symbian :(
nd...@gmail.com <nd...@gmail.com> #76
Shocked to discover this shortcomng, even more shocked to see that this has been ignored for years...
ma...@gmail.com <ma...@gmail.com> #77
I dont expect anyone from google read this, but let you know that i have spend a lot of money on my tablet, and after discovering that i cannot undo after a huge text block ripping by mistake, i have thrown it away, bought a 200$ window$ netbook, and now i am much more satisfied. Tablets for taking notes on the run is simply waste of time and money, cursor is also sooooo slow, cant move word by word, and (guess that) you cannot undo typing at all! I'm disgusted by android quality as a netbook replacement.
ac...@gmail.com <ac...@gmail.com> #78
At first, members of the community show polite discontent and asked
Google, please, to take this matter seriously. After two years and
several updates, I agree, it's time to show a bit of anger. Perhaps
that's the recipe for them to take this issue on board. In my view,
Android has missed the point entirely ignoring the development of a
fancy input method for tablet displays - apart from being a better
experience browsing the internet, watching movies/pics and playing
games; faster, laptop-like typing is the only additional advantage
compared to smaller displays. We want undo NOW! Otherwise many Android
tablet users will get a quad-core iPad 3 when they are fed up of a
sluggish OS where productivity is a no-no.
Google, please, to take this matter seriously. After two years and
several updates, I agree, it's time to show a bit of anger. Perhaps
that's the recipe for them to take this issue on board. In my view,
Android has missed the point entirely ignoring the development of a
fancy input method for tablet displays - apart from being a better
experience browsing the internet, watching movies/pics and playing
games; faster, laptop-like typing is the only additional advantage
compared to smaller displays. We want undo NOW! Otherwise many Android
tablet users will get a quad-core iPad 3 when they are fed up of a
sluggish OS where productivity is a no-no.
bl...@gmail.com <bl...@gmail.com> #79
I have ICS but I can't find the "undo" when typing. Has it been added yet? It seems like a basic feature...
dd...@gmail.com <dd...@gmail.com> #80
No, it hasn't been added, despite having been requests for more than 2 years here and in other Google Code issues.
You can also see that nobody from @google.com ever replied, which means that Google doesn't give a shit on their own code.google.com Android issues, and you're better off with a custom ROM, where there might be a chance that Undo exists or gets implemented.
You can also see that nobody from @
no...@gmail.com <no...@gmail.com> #81
Undo - need function!
[Deleted User] <[Deleted User]> #82
No Undo on Android, is like being a drawer or a writer without a rubber.
Google thInks Android's users are God, like itself, never do a mistake mwahaha
Google thInks Android's users are God, like itself, never do a mistake mwahaha
ka...@gmail.com <ka...@gmail.com> #83
I have lost text from several emails and/or on web browsers after somehow hitting the wrong key. The lack of an "undo" key is unacceptable in this day and age. Honestly, people are paying hundreds (sometimes thousands) of dollars on android smart/super phones and tablets - there should be a list of criteria that are mandatory to include in systems such as Android, for quality control. I have lost countless hours through having this happen routinely - I do try to type in a word processing program and copy and paste - but I don't always remember to do this when replying to emails in a hurry. One of the sole purposes of the Android system is to be able to send and receive emails (and the like) - I consider an "undo" feature to be necessary, when typing - especially considering the sometimes sporadic behavior of touch pads. I was going to upgrade to a Google Nexus for my next phone, and buy an Asus Eee PC prime - I am certainly glad I discovered this issue first - as to purchase these systems as a university student in a professional program would be to throw my money away [without a rudimentary 'undo']...
qu...@gmail.com <qu...@gmail.com> #84
Issue pain x # of complaints
= Total level of pain
With the pain/sadness this issue causes multiplied by the number of complaints, are there any issues causing greater pain in the android community? Anyone have a list of those that are currently higher?
Out of curiosity, who decided leaving this out was more critical than inclusion? I assume that must have been a really cool discussion, or a really silly mistake, because this is quite painful.
= Total level of pain
With the pain/sadness this issue causes multiplied by the number of complaints, are there any issues causing greater pain in the android community? Anyone have a list of those that are currently higher?
Out of curiosity, who decided leaving this out was more critical than inclusion? I assume that must have been a really cool discussion, or a really silly mistake, because this is quite painful.
ke...@gmail.com <ke...@gmail.com> #85
How could you not have typing Undo on what is essentially a computer? This is the end of mankind as we know it! Apple has the UNDO typing feature!!!!!
How long with this take to program? Half-a-Day? A Week?
How long with this take to program? Half-a-Day? A Week?
se...@gmail.com <se...@gmail.com> #87
I found a way to undo!!!! I'm not sure if this will work for everyone but I found an app that has a keyboard to undo, it's called "A.I. type keyboard", I'm not sure if this download is available to everyone but I found it in the android market and I'm in Canada.
sc...@gmail.com <sc...@gmail.com> #88
A.I. type keyboard is indeed nice, just not sure I can go back to hunt-and-peck after Swype...
my...@gmail.com <my...@gmail.com> #89
It's not a defect, its a useless feature, if you can't retype something twice then there's something wrong with you. So what if its tedious? If its that important than jump on a computer
va...@gmail.com <va...@gmail.com> #90
mynameis...@gmail.com, not sure if you are serius or not or just using some jedi mind tricks to make google look dumb for excluding the feature so long, but thanks for the laugh either way.
my...@gmail.com <my...@gmail.com> #91
Well trust me when I say google probably agrees with me, and I'm also pretty damn sure that the feature would lie with the keyboard and not the os itself. That's why its so irrelevant, if you want it so bad then make your own keyboard capable of this.
If you want something do it yourself!
If you want something do it yourself!
be...@gmail.com <be...@gmail.com> #92
wow, so you were serious...I do think that undo is a little more complicated than one would think. However, the answer to someone who now owns a device costing as much as $600 is "you want that? Then make it yourself"?!? Sounds like a certain electronics company with a fruit logo :-)
ma...@mattclare.ca <ma...@mattclare.ca> #93
mynameis...@gmail.com, are you worried someone will ask you to make this?
Trust everyone else, it's important. The less-than-ideal selection methodology often replaces or cuts content that one didn't intend to select. When the selection, or accidental backspace, is of something very large, or includes inline media or URLs, it's a big deal. This might also mean it has to implemented above the keyboard level.
Undo functionality entered into most operating systems and applications before version 4.
I can see you're not the type to reflect, or perhaps edit, what you screed into your keyboard and thus are unlikely to need to revisit what you are composing, but for others, this would be useful.
Trust everyone else, it's important. The less-than-ideal selection methodology often replaces or cuts content that one didn't intend to select. When the selection, or accidental backspace, is of something very large, or includes inline media or URLs, it's a big deal. This might also mean it has to implemented above the keyboard level.
Undo functionality entered into most operating systems and applications before version 4.
I can see you're not the type to reflect, or perhaps edit, what you screed into your keyboard and thus are unlikely to need to revisit what you are composing, but for others, this would be useful.
my...@gmail.com <my...@gmail.com> #94
I own a total of $2100 worth of android devices and I will never ever touch anything with a fruit logo :)
My point is, google isn't going to do it. They don't care, they have better things to do. So if someone wants it that bad it needs to be either done with a keyboard dev or someone creating a custom Rom
My point is, google isn't going to do it. They don't care, they have better things to do. So if someone wants it that bad it needs to be either done with a keyboard dev or someone creating a custom Rom
an...@gmail.com <an...@gmail.com> #95
Obviously you're right that Google doesn't care. And the success of Android
despite of the Undo issue make them think it's ok. There isn't any media
coverage or pressure for this neither. But still it's a problem from a user
perspective that should be fixed, and it becomes more important with larger
devices (tablets) as people want to write on their mobile device instead of
the PC.
Am 12.03.2012 19:09 schrieb <android@googlecode.com>:
despite of the Undo issue make them think it's ok. There isn't any media
coverage or pressure for this neither. But still it's a problem from a user
perspective that should be fixed, and it becomes more important with larger
devices (tablets) as people want to write on their mobile device instead of
the PC.
Am 12.03.2012 19:09 schrieb <android@googlecode.com>:
cr...@gmail.com <cr...@gmail.com> #96
This isn't some obscure feature that can be easily added for .01% of users who want it. This is a critical function that needs to be built into the very soul of the operating system to work, and will be used by 99% of users on a daily basis. ESPECIALLY with an awkward touch-screen interface, it is very easy to accidentally delete a file, delete a block of text, or touch the screen wrong (and you're not sure if you accidentally just did something). This is a function that has been an integral part of every operating system since about 1990. mynameis, you're not being helpful - this is a critical update needed, they can forget about any other gimmick they want to integrate into their product until it works at a very basic level, which it does not without an undo macro built in.
dd...@gmail.com <dd...@gmail.com> #97
I tweeted to @Android about this https://twitter.com/#!/dandv/status/179371123820081152 . Not that I actually think they'll give a damn, unless we get like hundreds of retweets. In that case, I do have some media connections that could get us coverage.
bo...@gmail.com <bo...@gmail.com> #98
I retweeted your tweet
let's all do that & maybe they will get the point that we are hundreds of
people who represent millions who want this feature
let's all do that & maybe they will get the point that we are hundreds of
people who represent millions who want this feature
ri...@blakehome.com <ri...@blakehome.com> #99
This is really needs some more attention.
ri...@blakehome.com <ri...@blakehome.com> #100
Coming from an iPhone 4, I love my Galaxy Note. However, few things have made the me more frustrated than realizing that there is no freaking undo when my text just got wiped out.
ak...@gmail.com <ak...@gmail.com> #101
Just accidentally wiped out the work of 15 min careful typing with no undo to find. Using Gingerbread just a few days - to find out that one of the most basic feature does not even exist in an OS of this astounding richness of possibilities!
THANKS FOR ADDING THIS UNDO-FEATURE asap (better before asap ...)!!
THANKS FOR ADDING THIS UNDO-FEATURE asap (better before asap ...)!!
ca...@gmail.com <ca...@gmail.com> #102
Yes this is definitely a very important feature if you want to use a phone for writing long emails etc. I lost a very long email just now because I tried to copy it but accidentally hit a letter on the screen keyboard after selecting but before touching the selection to copy!
ma...@gmail.com <ma...@gmail.com> #103
Please add "undo". First smartphone, quite frustrating I cannot undo.
my...@gmail.com <my...@gmail.com> #104
Using Droid Charge. I seem to randomly stumble onto a typing mode with undo, but it's hard to reproduce, so I can only conclude that it's not really available when I need it. It's outrageous that such a fundamental text editor feature is not available on these supposedly modern advanced devices.
dh...@gmail.com <dh...@gmail.com> #105
Text edit UNDO feature is a huge need in Android. Please listen to your customers. If you're so against it, then please just add something like "Google Labs" for gmail that lets advanced users enable things not everyone wants. I love that aspect of gmail. You could just do something like that for android since it isn't a App thing, it is a system-wide text entry thing that can't be easily fixed with a simple free app download. Even less likely to be fixed w/ an app since I use a physical keyboard on my Epic. Lots of people also use physical keyboards with tablets, so please fix (or add options to enable in a "Labs" mode") this at the kernel level.
Thanks for listening to us.
Thanks for listening to us.
vi...@gmail.com <vi...@gmail.com> #106
WHY would an undo feature not be included?! It is a gross understatement, really, to say that this SHOULD BE included for text actions. PLEASE PLEASE PLEASE someone explain, with clarity, why Android does not provide this already -- forget that it "adds functionality" -- IT IS AN ESSENTIAL FUNCTION! A function as basic as copy/paste for someone who is writing!
Surely there is an undo on Android tablets?! Yes? No?! It seems not. Yikes! So what use is tablet for any sort of WORK?! If Android devices are meant to serve as toys, fair enough, forget an UNDO.
If Android is to be for work -- which presumes communicating (textually) -- then UNDO is vital, not an add-on, folks. VITAL.
This keeps me, by the way, from considering Android devices aside from my little, cost-effective LG phone via Virgin Mobile. I like it, but won't rely on it for anything, until there is UNDO. Also, this kills my considering a Chromebook, because it's showing that it is very much in the test stage. Android appeals to me, but backing off. Mac is reliable, even Windows, which I am always aggravated by at work, is at least not in some beta stage. I was unaward that Android is beta, but it will be until it gets and UNDO! What oversights will Chromebook have? Don't want to find out, now.
Getting a Macbook Pro instead. That's not gonna hurt Google any, but just saying. BIG HOLE in the operation sys without UNDO.
Google: "UNDO or UNDONE."
Surely there is an undo on Android tablets?! Yes? No?! It seems not. Yikes! So what use is tablet for any sort of WORK?! If Android devices are meant to serve as toys, fair enough, forget an UNDO.
If Android is to be for work -- which presumes communicating (textually) -- then UNDO is vital, not an add-on, folks. VITAL.
This keeps me, by the way, from considering Android devices aside from my little, cost-effective LG phone via Virgin Mobile. I like it, but won't rely on it for anything, until there is UNDO. Also, this kills my considering a Chromebook, because it's showing that it is very much in the test stage. Android appeals to me, but backing off. Mac is reliable, even Windows, which I am always aggravated by at work, is at least not in some beta stage. I was unaward that Android is beta, but it will be until it gets and UNDO! What oversights will Chromebook have? Don't want to find out, now.
Getting a Macbook Pro instead. That's not gonna hurt Google any, but just saying. BIG HOLE in the operation sys without UNDO.
Google: "UNDO or UNDONE."
bo...@gmail.com <bo...@gmail.com> #107
Not being able to undo/redo in simple text editing is a major flaw in android and should be giving topmost priority
sy...@gmail.com <sy...@gmail.com> #108
I would have thought it would be a standard feature off the cuff. Please please please add "Undo"
ir...@gmail.com <ir...@gmail.com> #109
I am new in the Android world - and discovered the lack of UNDO the hard way. Google search convinced me that there really is no way to get my text back :(. There was ctrl-z in my old good Windows Mobile 5...
la...@gmail.com <la...@gmail.com> #110
Please bring the UNDO functionality. This is ridiculous not to have.
tu...@gmail.com <tu...@gmail.com> #111
You guys are going make me go back to using my iPhone 4 and iOS 6 if you don't add UNDO in the next random candy-named OS you come up with!
de...@gmail.com <de...@gmail.com> #112
Seriously this is a huge problem for productivity on any platform. IOS has it as does Windows phone...
pe...@gmail.com <pe...@gmail.com> #113
It's ridiculous that android doesn't have undo!!!
bo...@gmail.com <bo...@gmail.com> #114
Google please fix this. It is a simple but fatal defect. If it gets hyped well it can dissuade from android. Pleeeeeeeeeease fix it now.
ta...@gmail.com <ta...@gmail.com> #115
Undo is such a basic function. Please add this asap!
ta...@gmail.com <ta...@gmail.com> #116
[Comment deleted]
mo...@gmail.com <mo...@gmail.com> #117
I just switched over from an iPhone to a Samsung Galaxy Note II. I'm really surprised that there isn't an undo function. Please implement at least a one level undo if worried about the stack.
ts...@gmail.com <ts...@gmail.com> #118
Come on Google. Undo function is an essential OS feature.
If you want market leadership, you don't want disgruntled users out here.
If stack is your problem, then at least give us an "Are you sure" screen,
If we inadvertently trigger a delete.
If you want market leadership, you don't want disgruntled users out here.
If stack is your problem, then at least give us an "Are you sure" screen,
If we inadvertently trigger a delete.
th...@gmail.com <th...@gmail.com> #119
JB 4.1.2 STILL no Undo...
really???
(originally I had a much more eloquent & reasoned post, but I've accidentally deleted it, and... well... there's no undo!)
really???
(originally I had a much more eloquent & reasoned post, but I've accidentally deleted it, and... well... there's no undo!)
ss...@gmail.com <ss...@gmail.com> #120
it is simple but effective to use undo. Why google ignores this.
ku...@gmail.com <ku...@gmail.com> #121
Why no undo function!?
go...@gmail.com <go...@gmail.com> #122
We need the undo feature.
ch...@gmail.com <ch...@gmail.com> #123
NEED UNDO!!!
an...@gmail.com <an...@gmail.com> #124
Undo/redo implementation for any TextView is 400 lines of code (including javadocs and comments). It's not a difficult problem. Add it to the SDK now.
Here is a sample implementation. Feel free to use it a an inspiration.
Here is a sample implementation. Feel free to use it a an inspiration.
th...@gmail.com <th...@gmail.com> #125
Here's to undo and redo appearing in Android in 2013!
ma...@gmail.com <ma...@gmail.com> #126
Are you kidding me?
Undo is necessary!
Can't believe it's not here.
Undo is necessary!
Can't believe it's not here.
mi...@gmail.com <mi...@gmail.com> #127
Absolutely necessary. CAN WE GET THIS GOING ALREADY?!
al...@gmail.com <al...@gmail.com> #128
It's extremely frustrating to be composing an email on my Nexus 7 and then to mistakenly highlight and backspace on a whole paragraph thus losing an entire email. This has happened to me several times and in all honesty I never see the highlighting of the paragraph. All I know the typing is gone and there is now way to undo the deletion on Android. Please, dear please, give us "Ctrl" or some way to undo any type of keyboard input and/or text deletions on our Android devices. Without this extremely necessary and rudimental feature it really hinders productivity.
ha...@gmail.com <ha...@gmail.com> #129
OKEY... its 4.2.1 now and still not freaking undo!!!
i mean my ipod 4 had it! and its a media player!!!
my defy didnt have it with cm10 and so does my htc one x with its sense rom...
no undo anywhere(jb photo delete and gmail undo dont count here!) we need a good undo such as the one of windows os where you can undo EVERYTHING! file transfers text edits tasks and so on...
ppl even wrote the implementation for google and they still dont use it...
i mean my ipod 4 had it! and its a media player!!!
my defy didnt have it with cm10 and so does my htc one x with its sense rom...
no undo anywhere(jb photo delete and gmail undo dont count here!) we need a good undo such as the one of windows os where you can undo EVERYTHING! file transfers text edits tasks and so on...
ppl even wrote the implementation for google and they still dont use it...
ka...@gmail.com <ka...@gmail.com> #130
This feature is a must have. We need to have it in the next update. I suggest to have it like the iPhone: shake and undo the typing.
Thanks.
Thanks.
sa...@gmail.com <sa...@gmail.com> #131
This is not a Nice to have feature but definitely a Must have!
pa...@gmail.com <pa...@gmail.com> #132
Can we please fix this one rapidly and quietly?
I cannot look any iPhone owner straight in the eye anywmore, when I tell them how I don't regret switching to Android ;)
I cannot look any iPhone owner straight in the eye anywmore, when I tell them how I don't regret switching to Android ;)
ch...@groundfloormusic.ca <ch...@groundfloormusic.ca> #133
Undo is no less essential on a smart phone than on a laptop or desktop computer. It's flatly absurd that there's still no undo on Android. Undo is about as important to me as copy and paste, and it's definitely more important than cut. I've cursed my Android phones more than once because an unintended delete of some important or lengthy text couldn't be undone. At this point - 30 years into personal computing, well over a decade into smart phones, and now more than 5 years into Android itself - what possible excuse can there be for the continued absence of something so fundamental?
le...@gmail.com <le...@gmail.com> #134
This is an essential feature, too much time has been wasted, especially when accidentally deleting huge chunks of text from certain finicky apps like facebook.
pr...@gmail.com <pr...@gmail.com> #135
I've Android 4.0.4 ICS installed on my Micromax A110 mobile. I miss the undo very much, sometimes accidently some large text might get deleted which required undoing.
Same happend with me I typed a big mail and then I was selecting whole message to copy it to other location and while selecting my finger moved above keypad and all message got replaced by 2-3 special characters, then there was not way to get it back, I had to retype the whole message again.
Please add undo feature ASAP and provide us patch for same.
Same happend with me I typed a big mail and then I was selecting whole message to copy it to other location and while selecting my finger moved above keypad and all message got replaced by 2-3 special characters, then there was not way to get it back, I had to retype the whole message again.
Please add undo feature ASAP and provide us patch for same.
jb...@android.com <jb...@android.com> #136
[Comment deleted]
jb...@android.com <jb...@android.com> #137
[Comment deleted]
jb...@android.com <jb...@android.com> #138
[Comment deleted]
en...@google.com <en...@google.com>
df...@gmail.com <df...@gmail.com> #145
How can lacking Undo for 7 years become obsolete? :) - is Undo generally obsolete now and replaced by something better?
ko...@slumpy.org <ko...@slumpy.org> #146
hear hear
un...@gmail.com <un...@gmail.com> #147
Undo needs to be implemented.
li...@gmail.com <li...@gmail.com> #148
Android already supports undo and redo.
You'll have to contact the keyboard developers to add undo/redo options.
You'll have to contact the keyboard developers to add undo/redo options.
vi...@gmail.com <vi...@gmail.com> #149
How is this obsolete? We still need this!
br...@gmail.com <br...@gmail.com> #150
I can't agree more, and it's just that easy and simple. Come on Google!!
li...@gmail.com <li...@gmail.com> #151
It's not obsolete, it's already implemented several years back.
You can undo with Ctrl+Z, and redo with Ctrl+Y.
But to access these commands, you'll either need to have a physical keyboard, or a software keyboard with either Ctrl added, or with undo/redo buttons.
You can undo with Ctrl+Z, and redo with Ctrl+Y.
But to access these commands, you'll either need to have a physical keyboard, or a software keyboard with either Ctrl added, or with undo/redo buttons.
ci...@gmail.com <ci...@gmail.com> #152
I feel it should have been part of the long press menu, next to copy / paste
df...@gmail.com <df...@gmail.com> #153
I'm typing this on the default Google keyboard - on a Google Nexus phone, newest Android version fully updated. No undo. This can't be right.
th...@gmail.com <th...@gmail.com> #154
Yep - exactly. You can get this feature on some keyboards, and of course, with a mechanical keyboard. Just not on the official google keyboard. Irony much.
ko...@slumpy.org <ko...@slumpy.org> #155
I am hereby contacting the developer of the built in keyboard, please add undo!
jb...@gmail.com <jb...@gmail.com> #156
By replying to this email chain, you're spamming all 880 users that have
starred this issue. Unless you have something constructive to add, please
stop replying. (Yes, I see the irony in sending this email...)
On Wed, Apr 19, 2017 at 6:13 PM, <buganizer-system@google.com> wrote:
starred this issue. Unless you have something constructive to add, please
stop replying. (Yes, I see the irony in sending this email...)
On Wed, Apr 19, 2017 at 6:13 PM, <buganizer-system@google.com> wrote:
to...@gmail.com <to...@gmail.com> #157
google nexus here with android 7.1.2 no undo on default google keyboard!!!
to...@gmail.com <to...@gmail.com> #158
good, 880 folks can now question closing unfixed issue :-)
sp...@gmail.com <sp...@gmail.com> #159
I want this feature too, but it seems to me that this is the wrong place to
ask for it. Android supports undo/redo, it seems you guys just want it
implemented for the keyboard(s) you use, so you should email the developer
of that app, even if it is the Google Keyboard team. It would be great if
Google implemented system wide undo/redo via some on screen option, but
that does not make much sense from a usability standpoint. You can probably
get this feature with a custom rom or other mod if you really want it.
On Wed, Apr 19, 2017 at 8:35 PM <buganizer-system@google.com> wrote:
ask for it. Android supports undo/redo, it seems you guys just want it
implemented for the keyboard(s) you use, so you should email the developer
of that app, even if it is the Google Keyboard team. It would be great if
Google implemented system wide undo/redo via some on screen option, but
that does not make much sense from a usability standpoint. You can probably
get this feature with a custom rom or other mod if you really want it.
On Wed, Apr 19, 2017 at 8:35 PM <buganizer-system@google.com> wrote:
gp...@gmail.com <gp...@gmail.com> #160
da...@thekochfamily.net <da...@thekochfamily.net> #161
We don't want Undo keys on our keyboards any more than we want Cut or Paste keys; we don't even need a Ctrl key. Cut/Copy/Paste are done through the text field's long-press menu, and Undo/Redo should be as well.
Ironically perhaps, basic Undo/Redo (with menu items) was actually implemented shortly before this issue was closed - but apparently it had a possible crash so it was immediately reverted rather than fixed:https://github.com/android/platform_frameworks_base/commit/f59152cf00520d1bd36949b44faca2e1fcf6d28f
Oh, and if the emails are bugging you, just unstar the page. Seems there's little point keeping track of this now.
Ironically perhaps, basic Undo/Redo (with menu items) was actually implemented shortly before this issue was closed - but apparently it had a possible crash so it was immediately reverted rather than fixed:
Oh, and if the emails are bugging you, just unstar the page. Seems there's little point keeping track of this now.
qu...@gmail.com <qu...@gmail.com> #162
Had to switch to iOS to get this unfortunately, where you shake the phone
to undo. I believe Samsung implemented this on some of their phones as
well.
The fact that android adamantly refuses to do this makes me wonder if it
isn't some sort of patent issue that they don't want to deal with.
On Wed, Apr 19, 2017 at 7:42 PM <buganizer-system@google.com> wrote:
to undo. I believe Samsung implemented this on some of their phones as
well.
The fact that android adamantly refuses to do this makes me wonder if it
isn't some sort of patent issue that they don't want to deal with.
On Wed, Apr 19, 2017 at 7:42 PM <buganizer-system@google.com> wrote:
gp...@gmail.com <gp...@gmail.com> #163
pe...@gmail.com <pe...@gmail.com> #164
Needs to be in long press menu. Ridiculous it's not standard.
mr...@gmail.com <mr...@gmail.com> #165
jo...@gmail.com <jo...@gmail.com> #166
It's not the "keyboard" that needs undo, it's the text field itself, what many gui toolkits would call the "widget".
All system "widgets" (or whatever the gui text field is) for editable text should have an ability to do this. It should be opt out not opt in. (Undoable by default without the developer putting any work in). It should just be part of the
In most widget systems, as a developer of apps, you get this for free. Android is one of the only systems I've ever used that doesn't offer this in the long press menu by default. I've written code for a ton of other platforms, they pretty much all offer undo for free in all text fields. It's part of the os or more specifically, the gui toolkit.
This shouldn't be the keyboard's responsibility, but the textField itself's. Text fields, by default, should have feature in their long press menu.
I can't believe it's 2017 and this still isn't fixed. Has been the single most pressing issue/problem on Android for many years now.
All system "widgets" (or whatever the gui text field is) for editable text should have an ability to do this. It should be opt out not opt in. (Undoable by default without the developer putting any work in). It should just be part of the
In most widget systems, as a developer of apps, you get this for free. Android is one of the only systems I've ever used that doesn't offer this in the long press menu by default. I've written code for a ton of other platforms, they pretty much all offer undo for free in all text fields. It's part of the os or more specifically, the gui toolkit.
This shouldn't be the keyboard's responsibility, but the textField itself's. Text fields, by default, should have feature in their long press menu.
I can't believe it's 2017 and this still isn't fixed. Has been the single most pressing issue/problem on Android for many years now.
co...@gmail.com <co...@gmail.com> #167
I hope whoever restarted this stupid comment spam realizes that in the last few hours, almost 100 people have unstarred this bug because of them. Actually, make that 101.
pe...@gmail.com <pe...@gmail.com> #168
Seems like enough people want this, how do we get google to listen?
jo...@gmail.com <jo...@gmail.com> #169
>> I hope whoever restarted this stupid comment spam realizes
>> that in the last few hours, almost 100 people have unstarred
>> this bug because of them.
In order to prevent "spam", if google has official decided to never implement this, (even if for some reason we will never comprehend) this thread itself should be locked so that no one but ranking developers can post in it or reply. Then no one will get any more "spam" msgs about this.
If people don't want to see discussion about this, then unstarring the thread really is the right thing for them to do.
>> that in the last few hours, almost 100 people have unstarred
>> this bug because of them.
In order to prevent "spam", if google has official decided to never implement this, (even if for some reason we will never comprehend) this thread itself should be locked so that no one but ranking developers can post in it or reply. Then no one will get any more "spam" msgs about this.
If people don't want to see discussion about this, then unstarring the thread really is the right thing for them to do.
pu...@gmail.com <pu...@gmail.com> #170
I would like to double star this thread and add another star for every year
undo/redo is not implemented in the long press button menu. For more than 8
years you can just shake any osx device for a redo/undo and still there is
no proper solution for Android. I guess android users has just no use in
undo/redo - they never make mistakes.
On Thu, Apr 20, 2017 at 7:27 AM, <buganizer-system@google.com> wrote:
undo/redo is not implemented in the long press button menu. For more than 8
years you can just shake any osx device for a redo/undo and still there is
no proper solution for Android. I guess android users has just no use in
undo/redo - they never make mistakes.
On Thu, Apr 20, 2017 at 7:27 AM, <buganizer-system@google.com> wrote:
li...@gmail.com <li...@gmail.com> #171
Can you people please contact the Google Keyboard team about this instead? This isn't about the Android system itself.
pu...@gmail.com <pu...@gmail.com> #172
uhm YES it is about the android and NOT the keyboard. It should be
implemented in the long press button menu - please android !
On Thu, Apr 20, 2017 at 9:45 AM, <buganizer-system@google.com> wrote:
implemented in the long press button menu - please android !
On Thu, Apr 20, 2017 at 9:45 AM, <buganizer-system@google.com> wrote:
li...@gmail.com <li...@gmail.com> #173
The long press menu is about selected text, which has nothing to do with undo/redo. Instead of trying to bodge the functions into a menu where they don't belong, how about putting them somewhere where it make sense?
...perhaps on the keyboard?
The next update to the Gboard will feature a menu for cursor movement, copy/paste, and undo/redo would fit nicely into that menu. If Gboard adds these functions, then other keyboard developers will follow suit.
...perhaps on the keyboard?
The next update to the Gboard will feature a menu for cursor movement, copy/paste, and undo/redo would fit nicely into that menu. If Gboard adds these functions, then other keyboard developers will follow suit.
ri...@gmail.com <ri...@gmail.com> #174
The function itself has to be build into the OS for the keyboard to activate it.
Think about it: You can use CTRL+Z on your keyboard to undo in Windows, but if you connect the same keyboard to an Android device, it doesn't work.
Think about it: You can use CTRL+Z on your keyboard to undo in Windows, but if you connect the same keyboard to an Android device, it doesn't work.
li...@gmail.com <li...@gmail.com> #175
It is built into the OS already, it does work pressing Ctrl + Z, I have done that. It works in Google Chrome, Inbox, Play Store ... but it does not work in Facebook.
I would agree on making it more consistent and the default behaviour. But this topic is about "there's no way of undoing" which is false. A keyboard can have the undo feature on the keyboard and it'll work in Google apps.
What we need is a new topic about making undo a default feature. ...and we need Gboard to add an undo button.
I would agree on making it more consistent and the default behaviour. But this topic is about "there's no way of undoing" which is false. A keyboard can have the undo feature on the keyboard and it'll work in Google apps.
What we need is a new topic about making undo a default feature. ...and we need Gboard to add an undo button.
jo...@gmail.com <jo...@gmail.com> #176
>> The long press menu is about selected text
No, that really shouldn't be the case.
The long press is the "context menu" equivalent. Long press works on many things and is context sensitive.
When I long press inside a text widget, I should get menu options that pertain to that text widget. Where undo clearly belongs.
The reasons selection stuff is in there is because selecting text is something you want to do in the context of a text widget. (Alternatively, you could consider the context "the cursor" in this case.
Furthermore, if text is selected, and you long press on it, your context is that text and not necessarily the entire widget. Basically from a conceptual point of view text selection makes the context "the selected text" rather than the textfield itself.
Seriously, right here as I type this email, I can RMB click in the text field, and I see "undo" listed in the context menu. I can do that in a plethora of operating systems/gui toolkits/ applications. As a developer, I get that functionality *for free* in virtually all text widgets.
RMB click's existence as a de facto cross platform context menu example basically proves that it isn't keyboard related. Long press is just Android version of the context menu. This principle is generally well established and works all across Android in general, it's just missing here.
I can't believe there are people who don't seem to understand this basic concept of widgets having functionality built in related to how people will want to use them.
It's like having a spinner for a number entry field. A numerical entry field might have a default value, and in the long press on the spinner you could include a reset option. (Typically that's in the RMB context menu in existing desktop apps.)
It's a general case rule that widgets can be expected to have long press functionality.
This is not a "keyboard" thing. Keyboard are for entering characters. Undo shouldn't be some kind of keyboard macro, it should be built into each text widget, and each text widget should indpendently remember it's history. Undo in the keyboard would be a giant hack, ignoring where the functionality should be.
Personally, I'd actually be happy enough if undo was implemented in the keyboard, since at least for me, the problem would be solved from my (users) perspective. That would be terrible gui toolkit engineering though. A gui toolkit should have text widgets with undo built in. Win, qt, gtk, ios, apps all feature this. I'm as a developer, I should just declare a text field, and that text field should get "undo" ability without me having to do any work as a developer, and without having to rely on the user using a particular keyboard. It should work with any keyboard.
If it's just too much work to implement, fine, but the best answer is clear and obvious. The correct design is clearly undo in context menu (on long press) for text fields. However, maybe this is just one of those situations where for technical reasons we have to live with an implementation that doesn't live up to design potential.
No, that really shouldn't be the case.
The long press is the "context menu" equivalent. Long press works on many things and is context sensitive.
When I long press inside a text widget, I should get menu options that pertain to that text widget. Where undo clearly belongs.
The reasons selection stuff is in there is because selecting text is something you want to do in the context of a text widget. (Alternatively, you could consider the context "the cursor" in this case.
Furthermore, if text is selected, and you long press on it, your context is that text and not necessarily the entire widget. Basically from a conceptual point of view text selection makes the context "the selected text" rather than the textfield itself.
Seriously, right here as I type this email, I can RMB click in the text field, and I see "undo" listed in the context menu. I can do that in a plethora of operating systems/gui toolkits/ applications. As a developer, I get that functionality *for free* in virtually all text widgets.
RMB click's existence as a de facto cross platform context menu example basically proves that it isn't keyboard related. Long press is just Android version of the context menu. This principle is generally well established and works all across Android in general, it's just missing here.
I can't believe there are people who don't seem to understand this basic concept of widgets having functionality built in related to how people will want to use them.
It's like having a spinner for a number entry field. A numerical entry field might have a default value, and in the long press on the spinner you could include a reset option. (Typically that's in the RMB context menu in existing desktop apps.)
It's a general case rule that widgets can be expected to have long press functionality.
This is not a "keyboard" thing. Keyboard are for entering characters. Undo shouldn't be some kind of keyboard macro, it should be built into each text widget, and each text widget should indpendently remember it's history. Undo in the keyboard would be a giant hack, ignoring where the functionality should be.
Personally, I'd actually be happy enough if undo was implemented in the keyboard, since at least for me, the problem would be solved from my (users) perspective. That would be terrible gui toolkit engineering though. A gui toolkit should have text widgets with undo built in. Win, qt, gtk, ios, apps all feature this. I'm as a developer, I should just declare a text field, and that text field should get "undo" ability without me having to do any work as a developer, and without having to rely on the user using a particular keyboard. It should work with any keyboard.
If it's just too much work to implement, fine, but the best answer is clear and obvious. The correct design is clearly undo in context menu (on long press) for text fields. However, maybe this is just one of those situations where for technical reasons we have to live with an implementation that doesn't live up to design potential.
jo...@gmail.com <jo...@gmail.com> #177
> I would agree on making it more consistent and the default behaviour.
> But this topic is about "there's no way of undoing" which is false
Perhaps the text fields do have undo built in and it just isn't exposed by default?
In that case the text fields work well already, and it's just making sure that a menu exists somewhere for accessing them. Ideally that menu would exist by default in all declared text fields.
> But this topic is about "there's no way of undoing" which is false
Perhaps the text fields do have undo built in and it just isn't exposed by default?
In that case the text fields work well already, and it's just making sure that a menu exists somewhere for accessing them. Ideally that menu would exist by default in all declared text fields.
li...@gmail.com <li...@gmail.com> #178
>>>> The long press menu is about selected text
>>No, that really shouldn't be the case.
Yes, that is exactly the case.
You have:
• cut out selected text
• copy selected text
• paste and replace selected text
• make all text the selected text
• share selected text
• web search with selected text
• translate selected text
Undo/redo won't fit this.
• undo selected text???
>>No, that really shouldn't be the case.
Yes, that is exactly the case.
You have:
• cut out selected text
• copy selected text
• paste and replace selected text
• make all text the selected text
• share selected text
• web search with selected text
• translate selected text
Undo/redo won't fit this.
• undo selected text???
li...@gmail.com <li...@gmail.com> #179
>>Keyboard are for entering characters.
Gboard will have cut and copy features, and moving the cursor.
It currently have web search.
>> long press [...] (Typically that's in the RMB context menu in existing desktop apps.)
No, in Android, long press is solely for selection. You have the context options at the top. This is part of the Android design document.
>> right here as I type this email, I can RMB click in the text field, and I see "undo" listed in the context menu.
I don't know what client you are using, but you might find "settings", "inspect element", other extension options. A lot of things that has nothing to do with the selected text. But that doesn't mean Android should do the same thing.
Gboard will have cut and copy features, and moving the cursor.
It currently have web search.
>> long press [...] (Typically that's in the RMB context menu in existing desktop apps.)
No, in Android, long press is solely for selection. You have the context options at the top. This is part of the Android design document.
>> right here as I type this email, I can RMB click in the text field, and I see "undo" listed in the context menu.
I don't know what client you are using, but you might find "settings", "inspect element", other extension options. A lot of things that has nothing to do with the selected text. But that doesn't mean Android should do the same thing.
jo...@gmail.com <jo...@gmail.com> #180
>>>> The long press menu is about selected text
>>No, that really shouldn't be the case.
>Yes, that is exactly the case.
Your example has a flaw: You assume the only context available in a text field is the "selected text context". That isn't true.
If no text is selected, then the long press on the text widget (perhaps on empty space) is the context of the text widget, not the selected text.
I just tried this in Firefox on windows. You can try it yourself and see. It works very well.
If I type text into a field and right click on the field with no text selected, undo shows up.
If I have text selected and right click on that text, undo doesn't show up.
That's correct and expected behaviour..
The context menu for the text field has options not just about the selected text, but pertaining to the text field.
The context menu for the selected text itself has options specifically for the selected text.
This is pretty standard practice across most applications in many operating systems. Android could definitely do it too.
This even sort of already holds true on Android. I just tried it on Android and *it already has a different context menu in Android* depending on selection status. When no text is selected I get the a menu of [ Paste, Select All ]
When I select text I get [ Cut, Copy, Paste, ... ]
So it's already most there, even in Android. The frameworks all there, and everything does already work the way I've described. The short no selection context menu is simply missing "undo". [ Paste, Select All ] simply needs to be [ Paste, Select All, Undo ].
Note that in this case, the entries [ Paste, and Select All ] aren't in the context of the selected text, it's in the context of the text field. Paste and Select All are both things you can do in a text field. They don't depend on an existing selection of text.
>>No, that really shouldn't be the case.
>Yes, that is exactly the case.
Your example has a flaw: You assume the only context available in a text field is the "selected text context". That isn't true.
If no text is selected, then the long press on the text widget (perhaps on empty space) is the context of the text widget, not the selected text.
I just tried this in Firefox on windows. You can try it yourself and see. It works very well.
If I type text into a field and right click on the field with no text selected, undo shows up.
If I have text selected and right click on that text, undo doesn't show up.
That's correct and expected behaviour..
The context menu for the text field has options not just about the selected text, but pertaining to the text field.
The context menu for the selected text itself has options specifically for the selected text.
This is pretty standard practice across most applications in many operating systems. Android could definitely do it too.
This even sort of already holds true on Android. I just tried it on Android and *it already has a different context menu in Android* depending on selection status. When no text is selected I get the a menu of [ Paste, Select All ]
When I select text I get [ Cut, Copy, Paste, ... ]
So it's already most there, even in Android. The frameworks all there, and everything does already work the way I've described. The short no selection context menu is simply missing "undo". [ Paste, Select All ] simply needs to be [ Paste, Select All, Undo ].
Note that in this case, the entries [ Paste, and Select All ] aren't in the context of the selected text, it's in the context of the text field. Paste and Select All are both things you can do in a text field. They don't depend on an existing selection of text.
jo...@gmail.com <jo...@gmail.com> #181
>> long press [...] (Typically that's in the RMB context menu in existing desktop apps.)
>No, in Android, long press is solely for selection. You have the context options at the top. This is part of the Android design document.
That clearly isn't entirely true, since "paste" isn't something done with the selected text. Paste isn't a "selecting text" action. There's already is a different menu without a text selection. Also, the design does't hold up, because even if the design docs say otherwise, long press is commonly used in android apps to access menus that are related to what was long pressed. I just tried, and many apps show this functionality, where long press is in fact used as a context menu. Frankly that works well, and seems to be the only way to get a context menu for things that aren't selectable, which many apps do have.
Possibly the Android design document just didn't take this into consideration. Given the importance of undo for text fields, it might be worth presenting this issue to the designers there. Most other GUI toolkits have take explicit consideration for this. (menus that exist for using functions of the text field itself, of which selections are a subset)
However, I do think that your explanation about the design document does at least, finally, explain why it works the way it does, and why the designers and developers are reluctant to change it. I don't personally think that's a good design, but at least I can finally understand the reasoning behind why someone wouldn't want it in the context menu. (or as you say "the selection menu").
In which case, even if this may have seemed like needless discussion, we did at least get to the core of the problem, and the root of the disagreement. It essentially seems to boil down to some designer somewhere saying "long presses should only be about text selection not editing" (even if that's self inconsistent, having cut/paste etc (which are editing functions not selection functions, even though they happen to be aware of the selection when they do their editing). Basically the root of the problem is that the Android design doc specifies something that seems unreasonable to some of us.
So yeah, at least this should give a clear explanation to anyone who doesn't understand the reasoning behind why it won't be implemented as a context menu. Thanks for explaining. I'll be happy enough with a keyboard based solution, since it will solve my problem, even if I consider Android to be ugly and hackish in its design for this matter.
>No, in Android, long press is solely for selection. You have the context options at the top. This is part of the Android design document.
That clearly isn't entirely true, since "paste" isn't something done with the selected text. Paste isn't a "selecting text" action. There's already is a different menu without a text selection. Also, the design does't hold up, because even if the design docs say otherwise, long press is commonly used in android apps to access menus that are related to what was long pressed. I just tried, and many apps show this functionality, where long press is in fact used as a context menu. Frankly that works well, and seems to be the only way to get a context menu for things that aren't selectable, which many apps do have.
Possibly the Android design document just didn't take this into consideration. Given the importance of undo for text fields, it might be worth presenting this issue to the designers there. Most other GUI toolkits have take explicit consideration for this. (menus that exist for using functions of the text field itself, of which selections are a subset)
However, I do think that your explanation about the design document does at least, finally, explain why it works the way it does, and why the designers and developers are reluctant to change it. I don't personally think that's a good design, but at least I can finally understand the reasoning behind why someone wouldn't want it in the context menu. (or as you say "the selection menu").
In which case, even if this may have seemed like needless discussion, we did at least get to the core of the problem, and the root of the disagreement. It essentially seems to boil down to some designer somewhere saying "long presses should only be about text selection not editing" (even if that's self inconsistent, having cut/paste etc (which are editing functions not selection functions, even though they happen to be aware of the selection when they do their editing). Basically the root of the problem is that the Android design doc specifies something that seems unreasonable to some of us.
So yeah, at least this should give a clear explanation to anyone who doesn't understand the reasoning behind why it won't be implemented as a context menu. Thanks for explaining. I'll be happy enough with a keyboard based solution, since it will solve my problem, even if I consider Android to be ugly and hackish in its design for this matter.
ko...@slumpy.org <ko...@slumpy.org> #182
I would like to add that whoever is still annoyed by the "spam" is most welcome to unstar this. Obviously without the discussion that has just taken place nothing more would have been done with this ticket as it was closed, so your precious stars didn't mean much anyway.
jo...@gmail.com <jo...@gmail.com> #183
Ultimately, what I realize after using a bunch of other "official" Google apps is that the context menu of a widget is generally accessed by the little three dots, icon, not long press. Even while, at the same time, many other apps have context menus as longpress, which makes it inconsistent for users.
So the real issue here is that design standard text fields don't really have *any* context menu, which seems crazy, but essentially is the design standard on Android. I don't expect it to happen, but given the importance of text editing in all text fields, my own suggestion for solving that problem would be re-spec of longpress on text fields as the "text editing menu" rather than the "text selection menu", for which text selection is a subset of the entries. That already is sort of the case unofficially, already having cut/copy/paste since those are editing features not text selection features.
An alternate solution that wouldn't break the design standard would be for text fields to have a context menu accessible somewhere via a "..." button, and having undo be a part of that context menu. As a user I'd appreciate all text fields having that by default, but I can understand why the designers wouldn't want this.
At least both sides of this debate should be pretty clearly understandable now.
So the real issue here is that design standard text fields don't really have *any* context menu, which seems crazy, but essentially is the design standard on Android. I don't expect it to happen, but given the importance of text editing in all text fields, my own suggestion for solving that problem would be re-spec of longpress on text fields as the "text editing menu" rather than the "text selection menu", for which text selection is a subset of the entries. That already is sort of the case unofficially, already having cut/copy/paste since those are editing features not text selection features.
An alternate solution that wouldn't break the design standard would be for text fields to have a context menu accessible somewhere via a "..." button, and having undo be a part of that context menu. As a user I'd appreciate all text fields having that by default, but I can understand why the designers wouldn't want this.
At least both sides of this debate should be pretty clearly understandable now.
ko...@slumpy.org <ko...@slumpy.org> #184
> Ultimately, what I realize after using a bunch of other "official" Google apps is that the context menu of a widget is generally accessed by the
> little three dots, icon, not long press. Even while, at the same time, many other apps have context menus as longpress, which makes it
> inconsistent for users.
I disagree with your assessment that the context menu of a widget is accessible with the three dot menu. The three dot menu is for the general "view" context and not for a specific widget inside the view (example, press on the three dots while composing an email in the gmail app and all the options relate to the email, not the content).
> little three dots, icon, not long press. Even while, at the same time, many other apps have context menus as longpress, which makes it
> inconsistent for users.
I disagree with your assessment that the context menu of a widget is accessible with the three dot menu. The three dot menu is for the general "view" context and not for a specific widget inside the view (example, press on the three dots while composing an email in the gmail app and all the options relate to the email, not the content).
st...@gmail.com <st...@gmail.com> #185
I also would like Undo to be easily accessible and added to the long press
options by default on Android systems.
So, if Undo is actually supported and implemented by text fields on
Android, that can be triggered by some keyboards, how much work/developer
hours would be to add an additional "Undo" option below "Paste" in long
press context menu (or cursor action popup - whatever it is called) to
trigger undo functionality?
Is there a technical issue? Or is this mostly UI design concept issue where
the resistance is coming from? Where would be the best place we can
lobby/vote/request this feature?
Üdvözlettel,
Szikra Istvan
On Thu, Apr 20, 2017 at 11:46 AM, <buganizer-system@google.com> wrote:
options by default on Android systems.
So, if Undo is actually supported and implemented by text fields on
Android, that can be triggered by some keyboards, how much work/developer
hours would be to add an additional "Undo" option below "Paste" in long
press context menu (or cursor action popup - whatever it is called) to
trigger undo functionality?
Is there a technical issue? Or is this mostly UI design concept issue where
the resistance is coming from? Where would be the best place we can
lobby/vote/request this feature?
Üdvözlettel,
Szikra Istvan
On Thu, Apr 20, 2017 at 11:46 AM, <buganizer-system@google.com> wrote:
mk...@gmail.com <mk...@gmail.com> #186
Android O is testing custom navbar buttons, but Undo/Redo aren't an option due to a lack of corresponding keycodes:
http://www.androidpolice.com/2017/03/22/add-permanent-leftright-cursor-buttons-nav-bar-android-o/
https://developer.android.com/reference/android/view/KeyEvent.html
I've filed Issue 37553921 to ask that Undo/Redo keycodes be added to the API. The placement wouldn't be ideal, but it'd sure beat having nothing:
https://issuetracker.google.com/issues/37553921
I've filed
bi...@gmail.com <bi...@gmail.com> #187
ASSIGN BUG TO ANDROID KEYBOARD TEAM.
This is political maneuvering, plain and simple.
I expected integrity from Google.
On Apr 19, 2017 5:29 PM, <buganizer-system@google.com> wrote:
This is political maneuvering, plain and simple.
I expected integrity from Google.
On Apr 19, 2017 5:29 PM, <buganizer-system@google.com> wrote:
ry...@gmail.com <ry...@gmail.com> #188
I really can't believe what's happening in this issue thread. The decision to declare the status as: won't fix and obsolete seems like it comes from an absurdist comedy. It is a vital function with more and more people using their smart phones to perform increasing complex tasks. Long emails and posts can be erased by a single misplaced finger press. It's happened to me and it is immeasurably frustrating and in some circumstances very costly.
User's need the ability to undo and redo in any text field in any app running on Android. They don't care too much how it is implemented only that it is available on stock Android without the user having to go out of his way to install some kind of third party software to use it. After all you don't know that you need this feature until it's too late. Someone at Google needs to take responsibility and implement it. I don't think this discussion about the best place to implement the undo/redo feature is helpful. Either in the long press menu or on the keyboard would be fine. Just get it done.
User's need the ability to undo and redo in any text field in any app running on Android. They don't care too much how it is implemented only that it is available on stock Android without the user having to go out of his way to install some kind of third party software to use it. After all you don't know that you need this feature until it's too late. Someone at Google needs to take responsibility and implement it. I don't think this discussion about the best place to implement the undo/redo feature is helpful. Either in the long press menu or on the keyboard would be fine. Just get it done.
ca...@gmail.com <ca...@gmail.com> #189
It could be implemented by shaking the phone, like, you know, the iphone
ko...@slumpy.org <ko...@slumpy.org> #190
I think shake is a bad choice since it can be invoked accidentally too easily, and since there is no obvious "Redo" action...
go...@gmail.com <go...@gmail.com> #191
On the iPhone implementation it displays a pop up window after you shake the phone that allows you to implicitly select undo so it's not accidentally triggered.
au...@gmail.com <au...@gmail.com> #192
Why not set up the shift key for a triple tap to do a control and then
normal control keyboard functions to be enabled?
On Sat, Apr 22, 2017, 11:35 AM <buganizer-system@google.com> wrote:
normal control keyboard functions to be enabled?
On Sat, Apr 22, 2017, 11:35 AM <buganizer-system@google.com> wrote:
pa...@gmail.com <pa...@gmail.com> #193
The iPhone shaking gesture is an unintuitive and impractical gimmick and should not be implemented this way. Android also runs on more than just phones.
bi...@gmail.com <bi...@gmail.com> #194
For the record I bought the first Android phone in the first hours of
availability. Also, I'm an old hand in IT for what it's worth.
This Issue request is simply to implement an UNDO function in stock Android.
We are no design team for the feature request and any suggestions here will
not be run past the design team eg shaking the device. Nor should this
discussion be cluttered with out of scope requests eg CONTROL key.
Stick with UNDO. GIVE ME AN UNDO BUTTON. What the heck? My calculator has
an UNDO button.
The last time an accidental screen press erased a rare long and beautiful
stream of typing I thought long and hard about switching to Apple.
Closing this issue out of obsolete and saying "it's in the OS, just not our
keyboard. Too bad for you." is infuriating and in spite of all the things I
dislike about Apple is another nudge for me change my computing ecosphere.
Gee whiz Google. Is this a legal IP related issue? This is all I can think
of at this point.
Be honest, because the way this ticket is being handled stinks like a
rotten fish.
My Nexus 6P is dying and I need to make a decision soon.
GIVE ME STOCK UNDO. WTF?
Regards,
Bill Burton
On Apr 22, 2017 10:42 AM, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the
team that works on this product.
https://issuetracker.google.com/issues/36913735
*Changed*
*pa...@gmail.com <pa...@gmail.com> added note: *
The iPhone shaking gesture is an unintuitive and impractical gimmick and
should not be implemented this way. Android also runs on more than just
phones.
_______________________________
*Reference Info: 36913735 Undo typed text in text input*
component: Android Public Tracker > Text
status: Obsolete
reporter: vi...@gmail.com
cc: vi...@gmail.com
type: Feature Request P3 S3
duplicate issue: 36923961 <https://issuetracker.google.com/issues/36923961 >,
36929108 <https://issuetracker.google.com/issues/36929108 >, 36937739
<https://issuetracker.google.com/issues/36937739 >, 36966244
<https://issuetracker.google.com/issues/36966244 >, 36967056
<https://issuetracker.google.com/issues/36967056 >, 36978627
<https://issuetracker.google.com/issues/36978627 >, 36990993
<https://issuetracker.google.com/issues/36990993 >
AOSP ID: 6458
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker issue 36913735
<https://issuetracker.google.com/issues/36913735 > where you have the role:
starred.
availability. Also, I'm an old hand in IT for what it's worth.
This Issue request is simply to implement an UNDO function in stock Android.
We are no design team for the feature request and any suggestions here will
not be run past the design team eg shaking the device. Nor should this
discussion be cluttered with out of scope requests eg CONTROL key.
Stick with UNDO. GIVE ME AN UNDO BUTTON. What the heck? My calculator has
an UNDO button.
The last time an accidental screen press erased a rare long and beautiful
stream of typing I thought long and hard about switching to Apple.
Closing this issue out of obsolete and saying "it's in the OS, just not our
keyboard. Too bad for you." is infuriating and in spite of all the things I
dislike about Apple is another nudge for me change my computing ecosphere.
Gee whiz Google. Is this a legal IP related issue? This is all I can think
of at this point.
Be honest, because the way this ticket is being handled stinks like a
rotten fish.
My Nexus 6P is dying and I need to make a decision soon.
GIVE ME STOCK UNDO. WTF?
Regards,
Bill Burton
On Apr 22, 2017 10:42 AM, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the
team that works on this product.
*Changed*
*pa...@gmail.com <pa...@gmail.com> added note: *
The iPhone shaking gesture is an unintuitive and impractical gimmick and
should not be implemented this way. Android also runs on more than just
phones.
_______________________________
*Reference Info: 36913735 Undo typed text in text input*
component: Android Public Tracker > Text
status: Obsolete
reporter: vi...@gmail.com
cc: vi...@gmail.com
type: Feature Request P3 S3
duplicate issue: 36923961 <
36929108 <
<
<
<
<
<
AOSP ID: 6458
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker
<
starred.
v....@gmail.com <v....@gmail.com> #195
@comment 187.. Were too asking me to assign it? If so there is no change I can make to the defect.. I guess until the status is not changed this feature request will continued to be ignored
qu...@gmail.com <qu...@gmail.com> #196
This request is included in at least 7 other issues being tracked for about half a decade, to which my team is happy to be included, if the good folks at Google can suggest an intuitive, elegant solution?
Can we get a list of the currently recommended solutions? So that perhaps some folks can chose one that works for them.
It sounds like the intuitive, elegant solution is: "It's up to your keyboard developer to implement this." Is that correct?
Questions:
--Does the default keyboard for everyone on this thread include this?
--Does Google/Android nudge/encourage developers to include this option in their documentation
--How do we go about putting in a request that this be included in the default android keyboard, and/or that an option to add this be included in the default keyboard?
Thanks folks!
(Other questions from the community?)
36923961 Undo
36929108 how to undo in text editting
36937739 Undo
36966244 UNDO!!!!!!!!!!!!!!!!!!!!!!!!!!!
36967056 Undo function
36978627 undo typing
36990993 Undo
Can we get a list of the currently recommended solutions? So that perhaps some folks can chose one that works for them.
It sounds like the intuitive, elegant solution is: "It's up to your keyboard developer to implement this." Is that correct?
Questions:
--Does the default keyboard for everyone on this thread include this?
--Does Google/Android nudge/encourage developers to include this option in their documentation
--How do we go about putting in a request that this be included in the default android keyboard, and/or that an option to add this be included in the default keyboard?
Thanks folks!
(Other questions from the community?)
36923961 Undo
36929108 how to undo in text editting
36937739 Undo
36966244 UNDO!!!!!!!!!!!!!!!!!!!!!!!!!!!
36967056 Undo function
36978627 undo typing
36990993 Undo
th...@gmail.com <th...@gmail.com> #197
This is not a keyboard issue. It's an OS issue.
Sent from my Pixel XL
On Apr 25, 2017 4:11 PM, <buganizer-system@google.com> wrote:
Sent from my Pixel XL
On Apr 25, 2017 4:11 PM, <buganizer-system@google.com> wrote:
ol...@gmail.com <ol...@gmail.com> #198
I unstarred this issue DAYS ago, why I'm still getting these emails??
On 25/04/2017 23:21, buganizer-system@google.com wrote:
On 25/04/2017 23:21, buganizer-system@google.com wrote:
ba...@gmail.com <ba...@gmail.com> #199
@qu...@gmail.com: I checked with my keyboards on the Galaxy S7.
- GBoard doesn't contain an Undo function. Maybe there is a gesture, but who knows those?
- The preinstalled Samsung keyboard doesn't either.
Regarding the placement of the function: I'd agree with those leaning towards including UNDO in the keyboards, since quite frequently the intended previous state is several UNDOs away, and by accidentially UNDOing too often maybe several UNDOs and some REDOs.
However, I'd prefer this to be included in the context menu as well. The risk of using an otherwise great keyboard only to accidentially significant typing effort, when it turns out the keyboard has no UNDO button, is too high. Additionally, intuition here depends on prior experience of each user (Ctrl-Z vs right-click), so it should preferably be available in both places. Since it cannot be enforced for all third-party keyboards, the context menu becomes especially important.
- GBoard doesn't contain an Undo function. Maybe there is a gesture, but who knows those?
- The preinstalled Samsung keyboard doesn't either.
Regarding the placement of the function: I'd agree with those leaning towards including UNDO in the keyboards, since quite frequently the intended previous state is several UNDOs away, and by accidentially UNDOing too often maybe several UNDOs and some REDOs.
However, I'd prefer this to be included in the context menu as well. The risk of using an otherwise great keyboard only to accidentially significant typing effort, when it turns out the keyboard has no UNDO button, is too high. Additionally, intuition here depends on prior experience of each user (Ctrl-Z vs right-click), so it should preferably be available in both places. Since it cannot be enforced for all third-party keyboards, the context menu becomes especially important.
sh...@gmail.com <sh...@gmail.com> #200
please remove me from this. This is an extremely old issue and I'm not
involved.
On 4/23/17 6:17 AM, buganizer-system@google.com wrote:
involved.
On 4/23/17 6:17 AM, buganizer-system@google.com wrote:
ss...@gmail.com <ss...@gmail.com> #201
how can something so basic like undo be missing STILL from android after all these years. from the world's most widely used os? it's really an embarassment.
li...@gmail.com <li...@gmail.com> #202
I still can't fathom why you refuse to have the undo button on the text-manipulation tool (keyboard), and instead wants it in the text selection menu.
If Gboard adds it to their keyboard, supporting undo will be a higher priority.
If Gboard adds it to their keyboard, supporting undo will be a higher priority.
pu...@gmail.com <pu...@gmail.com> #203
couldn't agree more - its pure embarrassment ! What is wrong ?
On Fri, May 26, 2017 at 12:23 AM, <buganizer-system@google.com> wrote:
On Fri, May 26, 2017 at 12:23 AM, <buganizer-system@google.com> wrote:
kl...@gmail.com <kl...@gmail.com> #204
This issue is marked as obsolete, thus please vote for the following new issue by starring it:
https://issuetracker.google.com/issues/37017015
ss...@gmail.com <ss...@gmail.com> #205
frankly i don't care where it is as long as it exists and is universal
On Fri, May 26, 2017 at 5:17 AM, <buganizer-system@google.com> wrote:
On Fri, May 26, 2017 at 5:17 AM, <buganizer-system@google.com> wrote:
ss...@gmail.com <ss...@gmail.com> #206
wa...@gmail.com <wa...@gmail.com> #207
Since this one has been closed as "Won't Fix (Obsolete)" i suspect all comments here go into the ether, not even reaching any developer. Interested people should star this issue:
https://issuetracker.google.com/issues/37017015
And possibly this issue:
https://issuetracker.google.com/issues/62133390
And possibly this issue:
un...@gmail.com <un...@gmail.com> #208
Most of us have lost text that we've typed into a webform or into an email using Chrome and/or Gmail on Android.
Currently, there are dozens of tickets in Google's bug tracker software bemoaning the lack of access to the Undo / Redo feature built into Android but inaccessible to users. These tickets keep getting tagged "Won't Fix" by developers.
I've suggested to CloudHQ that they provide an Undo / Redo extension for Chrome and Gmail that provides UI access to the Undo / Redo feature.
Google has provided UI access to Undo / Redo in their Android office apps including Docs and Sheets, but not in Chrome or Gmail.
Searching the Google Play Store for Undo, I found two imperfect apps that do not replace the keyboard but "listen" to what is typed to provide multiple Undo and Redo.
Inputting+ app -- This looked promising, with floating visual Undo / Redo / Find / Replace buttons. Doesn't work with web UI yet per developer (so no good for Chrome). Didn't work on my Android phone in other contexts. Might be a permissions issue. Might conflict with the keyboard contextual menu or cliptray. I don't know. Might just be out of date, per recent reviews. Reviewers on Google Play said that recent updates broke the app and that it hasn't been updated in a year.
Typing Control app -- This app uses the volume control long press up and down buttons for multiple Redo and Undo. This app worked for me in all contexts. The limitation is that this app only seems to work while the text box is in focus continuously. And it's not in the visual UI as users expect. What is missing is visual feedback. I'd suggest flashing an Undo or Redo icon over the text and/or using Undo / Redo sounds. (Also, the short-press feature of moving the cursor forward and backward seems does not function as expected, jumping the cursor on first use to the beginning or end of the text in the text area. Facebook has also had issues with cursor placement recently, so it may be an Android issue.)
Still, the biggest issue that causes the most heartache seems to be that neither Chrome nor Gmail has implemented a visually accessible UI for Undo/Redo for its text areas -- and this needs to be fixed.
In the meantime, the Typing Control app solves this with the fewest bugs and UI conflicts by using the Volume Up/Down buttons for Undo/Redo.
Currently, there are dozens of tickets in Google's bug tracker software bemoaning the lack of access to the Undo / Redo feature built into Android but inaccessible to users. These tickets keep getting tagged "Won't Fix" by developers.
I've suggested to CloudHQ that they provide an Undo / Redo extension for Chrome and Gmail that provides UI access to the Undo / Redo feature.
Google has provided UI access to Undo / Redo in their Android office apps including Docs and Sheets, but not in Chrome or Gmail.
Searching the Google Play Store for Undo, I found two imperfect apps that do not replace the keyboard but "listen" to what is typed to provide multiple Undo and Redo.
Inputting+ app -- This looked promising, with floating visual Undo / Redo / Find / Replace buttons. Doesn't work with web UI yet per developer (so no good for Chrome). Didn't work on my Android phone in other contexts. Might be a permissions issue. Might conflict with the keyboard contextual menu or cliptray. I don't know. Might just be out of date, per recent reviews. Reviewers on Google Play said that recent updates broke the app and that it hasn't been updated in a year.
Typing Control app -- This app uses the volume control long press up and down buttons for multiple Redo and Undo. This app worked for me in all contexts. The limitation is that this app only seems to work while the text box is in focus continuously. And it's not in the visual UI as users expect. What is missing is visual feedback. I'd suggest flashing an Undo or Redo icon over the text and/or using Undo / Redo sounds. (Also, the short-press feature of moving the cursor forward and backward seems does not function as expected, jumping the cursor on first use to the beginning or end of the text in the text area. Facebook has also had issues with cursor placement recently, so it may be an Android issue.)
Still, the biggest issue that causes the most heartache seems to be that neither Chrome nor Gmail has implemented a visually accessible UI for Undo/Redo for its text areas -- and this needs to be fixed.
In the meantime, the Typing Control app solves this with the fewest bugs and UI conflicts by using the Volume Up/Down buttons for Undo/Redo.
jo...@gmail.com <jo...@gmail.com> #209
So, people have been requesting this for well beyond a decade but Google still refuses to add a keyboard shortcut to users who are trying to use Android more and more in place of my work machine.
bo...@gmail.com <bo...@gmail.com> #210
That's correct - it's really sad that they can't figure out how to offer as an option. Maybe OpenAI will come out with a mobile operating system that can do it
ol...@gmail.com <ol...@gmail.com> #211
Undo typing is now available in the floating menu next to "Copy, cut, paste".
ch...@gmail.com <ch...@gmail.com> #212
You are right.
See my screenshot form my Galaxy S22+ with Android 13.
I guess this Issue can be closed then.
See my screenshot form my Galaxy S22+ with Android 13.
I guess this Issue can be closed then.
ma...@gmail.com <ma...@gmail.com> #213
I updated to Android 13 a few days ago and I do not see this feature on my
phone, a Pixel
On Sat, Mar 25, 2023, 08:36 <buganizer-system@google.com> wrote:
phone, a Pixel
On Sat, Mar 25, 2023, 08:36 <buganizer-system@google.com> wrote:
j....@gmail.com <j....@gmail.com> #214
Yeah, that might be Samsung only. Not Android as a whole. I don't have it on my pixel 7 pro.
un...@gmail.com <un...@gmail.com> #215
I just returned a brand new Pixel 7 because the UI made me sea sick (literally, not metaphorically, physically ill).
Samsung has adds their own UI features and prevents other truly terrible stock UI from appearing on their phones. (I'm looking at you, Android 13 QuickMenu Tiles with scrolling text.)
If Samsung has added Undo to the Cut-Copy-Paste Floating Bubble Menu in their latest modified version of Android 13, that's helpful. It should still be a stock feature for Gboard and other Android keyboards and available in the Floating Bubble Menu without having to install a helper app with Accessibility permissions with all the security exposure that entails.
We've been asking for Undo typing UI for at least 13 years.
Written on an LG K51 running Android 12 and Gboard. No Undo in sight.
Samsung has adds their own UI features and prevents other truly terrible stock UI from appearing on their phones. (I'm looking at you, Android 13 QuickMenu Tiles with scrolling text.)
If Samsung has added Undo to the Cut-Copy-Paste Floating Bubble Menu in their latest modified version of Android 13, that's helpful. It should still be a stock feature for Gboard and other Android keyboards and available in the Floating Bubble Menu without having to install a helper app with Accessibility permissions with all the security exposure that entails.
We've been asking for Undo typing UI for at least 13 years.
Written on an LG K51 running Android 12 and Gboard. No Undo in sight.
to...@gmail.com <to...@gmail.com> #216
th...@gmail.com <th...@gmail.com> #217
not here on my Pixel 6a either
bo...@gmail.com <bo...@gmail.com> #218
Not on my Samsung Fold 4 Android 13
On Sat, Mar 25, 2023, 9:45 PM <buganizer-system@google.com> wrote:
On Sat, Mar 25, 2023, 9:45 PM <buganizer-system@google.com> wrote:
pa...@gmail.com <pa...@gmail.com> #219
I am guessing those who claim it is implemented likely see this only in a certain app. Is ut possible it's a part of the keyboard app on newer Samsung models?
ec...@gmail.com <ec...@gmail.com> #220
This feature is not implemented in stock android. It is not helpful to report phones where it doesn't exist or to catalog third party software where it does. Thanks for the enthusiasm, but please keep the comments to discussions about implemention.
th...@gmail.com <th...@gmail.com> #221
I disagree. The more comments there are on here, the more attention this feature request gets. If you don't like it, you can unsubscribe.
un...@gmail.com <un...@gmail.com> #222
Since this has been marked Won't Fix for more than a decade, and Samsung is
the leading provider of Android phones, the possibility that Samsung is
implementing a fix for this issue as a stock feature on their phones is
promising.
I just can't believe how bad the UI on Pixel phones has become under
non-Samsung Android 13.
Why would we ever want oversized Quick Menu tiles with scrolling text
fields? Are we suddenly emulating Windows Phones and QVC?
Why regurgitate failed designs and ignore basic features like Undo?
On Sat, Mar 25, 2023, 1:54 PM <buganizer-system@google.com> wrote:
the leading provider of Android phones, the possibility that Samsung is
implementing a fix for this issue as a stock feature on their phones is
promising.
I just can't believe how bad the UI on Pixel phones has become under
non-Samsung Android 13.
Why would we ever want oversized Quick Menu tiles with scrolling text
fields? Are we suddenly emulating Windows Phones and QVC?
Why regurgitate failed designs and ignore basic features like Undo?
On Sat, Mar 25, 2023, 1:54 PM <buganizer-system@google.com> wrote:
pu...@gmail.com <pu...@gmail.com> #223
I think it is funny that we can send rockets to Mars but can't create an
"undo" button for an android phone - wouldn't chatgpt be able to solve this
problem ?
On Sat, Mar 25, 2023 at 9:55 PM <buganizer-system@google.com> wrote:
"undo" button for an android phone - wouldn't chatgpt be able to solve this
problem ?
On Sat, Mar 25, 2023 at 9:55 PM <buganizer-system@google.com> wrote:
th...@gmail.com <th...@gmail.com> #224
My solution has been to install 'Hacker Keyboard' and switch to it if I
need to undo or paste etc, and Gboard isn't doing it. It is a 'full size'
keyboard, and all the keyboard shortcuts. like CTRL + Z and CTRL + SHIFT +
Z work
On Sun, 26 Mar 2023 at 18:39, <buganizer-system@google.com> wrote:
need to undo or paste etc, and Gboard isn't doing it. It is a 'full size'
keyboard, and all the keyboard shortcuts. like CTRL + Z and CTRL + SHIFT +
Z work
On Sun, 26 Mar 2023 at 18:39, <buganizer-system@google.com> wrote:
Description
Platform: Nexus One (US-English)
Request for feature: Undo
Currently, there is no way to undo typing. For example, if I type something
and then use backspace to erase a part of it, I cannot un-erase.