Autocomplete menu broken on Atlassian Jira after upgrade from 53.0.2785.143 to 54.x (various)
Reported by
nn...@neulinger.org,
Nov 15 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36 Example URL: https://issues.jenkins-ci.org/browse/WEBSITE-240 Steps to reproduce the problem: 1. https://issues.jenkins-ci.org/browse/WEBSITE-240 2. click to make advanced search field display 3. type "tex" and then click on "text" in the autocomplete/suggestion popup. On 53.x - 'text' will populate in the search. On 54.x - nothing happens. Above URL is just an example of a publicly accessible jira site you can test with. What is the expected behavior? 'text' will populate. What went wrong? Nothing happens. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 54.0.2840.100 Channel: stable OS Version: UB16 Flash Version: Shockwave Flash 23.0 r0 https://support.atlassian.com/servicedesk/customer/portal/22/JSP-277859 Open issue with Atlassian. I realize this is probably something that they can code around, but it very clearly was a change in behavior from 53 to 54. (I was trying to diagnose/reproduce from my desktop and couldn't, but all other systems were showing the failure. As soon as I updated desktop (ub16 linux) to 54, it started showing same symptom as all the 54 windows boxes.)
,
Nov 15 2016
Ah, sorry, copied only part of the url, missed parms. https://issues.jenkins-ci.org/browse/WEBSITE-240?jql=
,
Nov 15 2016
click advanced over to the right of the magnifying glass
,
Nov 15 2016
FYI, confirmations of this from differnet users in multiple organizations that I support, on multiple platforms.
,
Nov 16 2016
Atlassian is also treating as a bug on their side: https://jira.atlassian.com/browse/JRA-63206
,
Nov 16 2016
Appears they are updating the selection range and then doing a execCommand insertText command but it doesn't update the page. chongz@ could this be anything caused by you?
,
Nov 16 2016
specifically I see
that.replaceValue = function(start, end, newValue) {
var jQueryReference = jQuery(that.field);
jQueryReference.selectionRange(start, end);
if (jQuery.browser.webkit) {
document.execCommand("insertText", false, newValue)
} else {
jQueryReference.selection(newValue)
}
var newEnd = jQueryReference.selectionRange().end;
jQueryReference.selectionRange(newEnd, newEnd)
}
execute
,
Nov 16 2016
,
Nov 17 2016
Narrow bisect points to: https://chromium.googlesource.com/chromium/src/+/530015339e3f6572d239432b69f77ebca1492f73 tkent@ can you take a look at this issue please? Thanks!
,
Nov 17 2016
The code in comment 7 depends on a WebKit-origin bug which I fixed. input.setSelectionRange() sets focus unnecessarily. execCommand() is ignored because there is no focused element. The fix would be: * Remove jQuery.browser.webkit code path, * Add .focus() before execCommand() etc. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by cbiesin...@chromium.org
, Nov 15 2016