In the Android app, if I start writing a comment, then change the screen orientation (usually because I'm commenting while running for a bus), I can no longer continue typing in the comment box. I can focus on the box, and bring the keyboard up, but typing does nothing.   Refreshing the question doesn't fix it either. The only way around it is to completely exit the question, and go back in.
66044
There's a bug in the Android app where a comment can be typed in but not posted, meaning the post button does nothing and I have to back out of the question and go back in to post the comment. This definitely happens when the screen rotates, and also other times but I haven't identified them exactly.  I have version 1.0.78.  Edit: This had stopped happening but now started happening again when I updated to Android 6.0.1, now with version 1.0.85.
7958
Since the last update (v1.0.85), I am getting all the question pages blank on the Android app. For those who are confused with the image, I'm using RtL (Right-to-Left) layout.        If I scroll down (quite a bit) I can see the question. But even then I cannot see the question title, the related comments or answers.         App Version: 1.0.85 Device Manufacturer: LGE Device Model: LG-D620   OS Version: 5.0.2 (152541901f156)
101351
I am using a Mac machine.  I asked a question, and then, someone answered it.    I clicked "Edit" to add a comment, and I would like to press Enter to go to a new line, but doing so submitted my comment and ended the edit instead.
123913
App version: 1.0.52  When you edit a question and rotate the screen while the "Getting preview" or "Posting edit" dialog is showing the app will crash.  12-25 21:38:07.033 E/AndroidRuntime(4768): FATAL EXCEPTION: main 12-25 21:38:07.033 E/AndroidRuntime(4768): Process: com.stackexchange.marvin, PID: 4768 12-25 21:38:07.033 E/AndroidRuntime(4768): java.lang.IllegalArgumentException: View=com.android.internal.policy.impl.PhoneWindow$DecorView{42440ba0 V.E..... R......D 0,0-684,192} not attached to window manager 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:370) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.view.WindowManagerGlobal.removeView(WindowManagerGlobal.java:299) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.view.WindowManagerImpl.removeViewImmediate(WindowManagerImpl.java:84) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.app.Dialog.dismissDialog(Dialog.java:329) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.app.Dialog.dismiss(Dialog.java:312) 12-25 21:38:07.033 E/AndroidRuntime(4768): at com.stackexchange.marvin.core.OperationThatCanFail$1.onPostExecute(OperationThatCanFail.java:81) 12-25 21:38:07.033 E/AndroidRuntime(4768): at com.stackexchange.marvin.core.OperationThatCanFail$1.onPostExecute(OperationThatCanFail.java:67) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.os.AsyncTask.finish(AsyncTask.java:632) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.os.AsyncTask.access$600(AsyncTask.java:177) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:645) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.os.Handler.dispatchMessage(Handler.java:102) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.os.Looper.loop(Looper.java:136) 12-25 21:38:07.033 E/AndroidRuntime(4768): at android.app.ActivityThread.main(ActivityThread.java:5097) 12-25 21:38:07.033 E/AndroidRuntime(4768): at java.lang.reflect.Method.invokeNative(Native Method) 12-25 21:38:07.033 E/AndroidRuntime(4768): at java.lang.reflect.Method.invoke(Method.java:515) 12-25 21:38:07.033 E/AndroidRuntime(4768): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785) 12-25 21:38:07.033 E/AndroidRuntime(4768): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) 12-25 21:38:07.033 E/AndroidRuntime(4768): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132) 12-25 21:38:07.033 E/AndroidRuntime(4768): at dalvik.system.NativeStart.main(Native Method) 12-25 21:38:07.035 W/ActivityManager(27384):   Force finishing activity com.stackexchange.marvin/.ui.AskOrEditQuestionActivity
31740
So code blocks in questions and answers on the android app (inline included) seem to be scared of me putting my finger in them. When I poke them, they only move over two columns!  (For clarity, these are the code blocks that overlap the TextArea view because they've been eating too much)  The intended behaviour here is that when I press my finger into a code block, the touch event should register a drag; at current, I try to scroll inside a code block and I end up switching to question or answer view instead, over and over.  EDIT:  Something tells me this is status-bydesign because the text is deliberately cut off (probably inviting you to click on the code block and expand it; UX Decision?):
19038
It's impossible to write this way, text gets deleted, windows change, random tabs open. I've tried every solution I came across but none actually solve it (some don't even work)  I've tried installing touchpad indicator, I've tried adding a syndaemon option from startup application, I tried the same but from the terminal, nothing works.  I Just want to disable the touchpad completely while typing, no scrolling, no moving the cursor, nothing.
14749
Sometimes I find myself start writing a question, or start answering a question, in the mobile app and there are times where I then reach my computer or find out I need to be more comfortable when writing it; I need my computer - a larger screen, keyboard.  The problem is that by opening the question in the desktop browser - my draft will not be there and so I find myself start over or need to look&amp;copy my text from the smartphone or email it, etc. Not particularly comfortable...    I think we need some sort of a syncing ability.
81818
I love screen, but it drives me nuts that I have to stop typing input, hit CTRL+A [, and then find what I need.  Is there a way to make the scroll wheel function normally, rather than scrolling commands?   Also, is it possible to enable Shift+PageUp/PageDn?
72029
This only happens with the top few feed items (new since refresh maybe, or actually, maybe feed items before the update are OK, ones after aren't) but when I drag right to left to scroll between questions as soon as i get half way it snaps back. Sometimes I can get it to scroll and when I can scrolling back (left to right) works fine.  I'm on a stock Nexus 5.  P.s. On the plus side the app has some really nice ui improvements.
40716
I'm using an Italian keyboard so I do not have backticks. The problem for me is not when I'm writing a question, because I can use the UI of course, but when I'm writing a comment I have to use the keyboard to format my text.  I know the Ctrl+K shortcut, but it's not working on comments, to me at least. I was wondering if there is an alternative char?
102990
The below bug doesn't always happen, but does most of the time. Steps to reproduce:  Go to any review queue Post a comment Edit the comment Click Save Edits  Result:  Obviously the red box above is the annoying bug...  :-)
94400
This question was posted using the Android App.  When posting questions using the Android application, tag selection can be a little tricky &amp; error-prone.  The web application provides an autocompletion list of suggestions as you type, but no such list appears in the Android app. It would be very useful if similar functionality could be implemented there.  Also it appears that entering a new tag is friction-free, as might happen when fat fingering a tag. As a demonstration I have tagged this question with a false tag.  It should not be this easy to create a new tag, as I would guess the majority of these cases would be mistakes.
103331
I have keyboard shortcuts enabled in my profile. They are great, so I can't imagine answering questions and navigating on SE without them now.   However, I don't expect them to be active when using the mobile web interface. But if you try to use the question search box on the mobile web interface, then you suddenly find the achievements box opening, or the inbox, or the keyboard shortcuts help overlay appearing. Actually entering an h or i or r into the search box is impossible however.   Try it yourself:   enable keyboard shortcuts in preferences  open the mobile web UI (there is a link at the bottom right) select the questions tab select the magnifying glass try and type some search terms   Please don't even load keyboard shortcuts on the mobile web UI. The keyboard isn't even available most of the time. Or at least disable them for the search box.
58956
If I write a comment, make a typo, submit the comment, and then notice the mistake and want to correct it by editing the comment, I can't do that as a keyboard-only user.  If I try to tab to the "edit" button, the focus goes from the timestamp of the comment, straight to the () delete button, skipping right over the "edit" button.  Could we please be able to tab to "edit"?  If you're confused as to why it's important that things be accessible without the mouse, please read up on . While I thankfully don't have any physical problems with using  a mouse, I'm using my time with a broken mouse to give accessibility feedback so that people who need it can get a better site experience.
99204
On the Android app, could we have the ability to flag comments we've previously upvoted? This is a fairly regular need for me, and I ran into it again earlier: I flag comments as obsolete when they are, and fairly often, one of them will be a comment I've upvoted.  For an example of a typical case: a comment suggests a great improvement to a question, I upvote it, the author performs that improvement, the comment is now obsolete and (on my PC) I flag it as obsolete. The comments get cleaned up and the question moves on.  There's a request that's been around since 2011 for the site itself: . It's implemented by SOUP (as described ), but the Android app doesn't have a SOUP available to add this functionality to the app for me.
86954
Changing the orientation of your device within the tag selection view while asking a question removes all selected tags and clears the textbox.     Steps to reproduce:     Ask a question (does not happen when editing) Edit tags Enter some text in the box  Select a tag from the suggestion list Repeat the previous two steps as many times as you care to Rotate the device (source / target orientation doesn't matter, just need to change it) All selected tags and text typed in the textbox are gone and must be re-entered   I've reproduced this using version 1.0.63 of the SE app on two devices:     HTC One E8 m2ss (the Hong Kong version) rooted and running stock 5.0.2 ATT Galaxy S3 i747, rooted and sim unlocked, running Slimkat 4.4.2.build.4.1.official ROM on Android 4.4.2
11562
Just installed Ubuntu 17.10 and it seems that the keyboard layout switching has changed its behavior.  In the previous version of Ubuntu (such as 16.04 Unity), if I have 3 different keyboard layouts (for example EN-TH-JA), hitting Super+Space would always cycle to the next layout in the same order (e.g. EN to TH to JA then back to EN).  However since Ubuntu 17.10, this is no longer the case. It cycles through the layout in the MRU (Most Recently Used) ordering. So suppose that the layout starts with EN, then I cycled to TH. Next time I hit Super+Space, it would give me EN instead of JA.   I tried to dig up and found that the culprit is the newly implemented DCONF settings inside org.gnome.desktop.input-sources and there seems to be no way to change this behavior.   So my question is: Is there a way to change this behavior to "static ordering" of keyboard layout switching?    (As a side-note, the new behavior is very bad when we have three or more layouts. Most of the time we as a user couldn't remember the MRU layouts, so layout switching is very inconvenient and much slower than already knowing what the next layout would be if static ordering is used.)  If there is no settings to change this behavior, where should I report this as a bug or a feature request?