Created attachment 8770998 [details] svgIssue.html User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160604131506 Firefox for Android Steps to reproduce: Using Firefox 48 beta on Android Lollipop, open the attached html file. Tap the circle or rectangle. Actual results: The UI associated with selecting text appears--"markers" at each end of the shape appear as if there's text in between, and there's a bar across the top with the check mark for copying text. Expected results: Nothing should have happened, as the user is not selecting text. Note: This does not happen in Android Firefox 47.0.
I'm able to reproduce this using: Device:Galaxy Note 3(5.0), Galaxy Note 5(6.0),Xiaomi Pad 2(5.02) Build:Beta - 48.0b6, Aurora - 49.0a2(2016-07-13), Nightly - 50.0a1(2016-07-14)
Mark this looks to be fallout from the new text selection handles. 47 is unaffected.
My quick thought was dup of  ? With the original UI scheme, it was our working assumption (at least as recently as ) that non-text bearing selections were ignoreable. The rules did indeed change with AccessibileCarets, and we've let this bit of incompatiblility remain gray-ish. Perhaps TYLin would care to comment further? I'm sure code can accommodate front-end one way or another.  Bug 1221335 - AccessibleCarets seem to select some things (images, etc) that contain no text  Bug 1119834 - Text selection action bar is shown on div element containing no text
Duping this makes sense.
Unsetting tracking nom for 49/50. We will track in the duplicate bug.
I think this is a separate issue from Bug 1221335. I can reproduce this issue on desktop browser. When single-clicking on the SVG circle or rectangle, AccessibleCaretManager::OnSelectionChanged() is called with a non-collapsed selection range. That's why the carets are shown. The question is: why is *single-clicking* on the SVG shape resulting a selection?  http://searchfox.org/mozilla-central/rev/ff0e3782b1c44ffd1a68ef8e9e4f8be3866741e2/layout/base/AccessibleCaretManager.cpp#137
Just to add, I am still seeing this issue on Firefox 49.0.2 on Android 6.0.1 (Samsung Galaxy S7).