User Agent: Mozilla/5.0 (Linux; Android 4.4.2; Nexus 5 Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.166 Mobile Safari/537.36 Build ID: 20151029024147 Firefox for Android Steps to reproduce: This only seems to happen with Firefox and Swype. Other browsers and other keyboards don't seem to be affected. See https://youtu.be/6V22X2gQRj0 for a screen capture showing it happening (at 1:44). 1. Install Swype and set it as active keyboard. 2. Go to https://en.m.wikipedia.org/wiki/Dog_Latin#Examples and tap the edit link 3. Tap on the word "doggerel" (with double square brackets around it). Swype should appear. 4. Swipe from the Swype button to the "?123" button next to it to bring up the directional keys 5. Tap right until the cursor is just to the right of both closing brackets 6. Press backspace twice Actual results: One bracket and the final "l" of the word "doggerel" are deleted. The cursor is between the word and the remaining bracket. Expected results: The two brackets are deleted and the word "doggerel" is left intact.
Phone is Motorola Moto X, first edition, upgraded to Android 5.1 (contrary to the UA above).
Component: Untriaged → Keyboards and IME
Product: Firefox → Firefox for Android
Version: 42 Branch → Firefox 42
Apologies, I was apparently using Phony when I posted the bug. Here's the true UA: Mozilla/5.0 (Android 5.1; Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Sounds similar to bug 1203260.
I'm also experiencing (and the video also demonstrates) bug 1203260, but the effect of this one is different. Additionally, that bug also happens with other keyboards (e.g. Hacker's Keyboard); I've only been able to reproduce this one with Swype.
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.