Last modified: 2014-10-07 21:33:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69243, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67243 - jQuery UI 1.9.2 autocomplete makes triggers content vanishing in Chrome, Opera next
jQuery UI 1.9.2 autocomplete makes triggers content vanishing in Chrome, Oper...
Product: MediaWiki
Classification: Unclassified
JavaScript (Other open bugs)
All All
: High major (vote)
: 1.24.0 release
Assigned To: Nobody - You can work on this!
: upstream
Depends on:
Blocks: wmf-deployment
  Show dependency treegraph
Reported: 2014-06-28 10:23 UTC by Rainer Rillke @commons.wikimedia
Modified: 2014-10-07 21:33 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---
aklapper: Backport_WMF+

Screenshot from Google Chrome 35 (74.27 KB, image/png)
2014-06-30 15:28 UTC, Andre Klapper

Description Rainer Rillke @commons.wikimedia 2014-06-28 10:23:44 UTC
Original bug title:
jQuery UI 1.9.2 autocomplete makes triggers content vanishing in Chrome, Opera next

This has been reported upstream as

Another issue was reported with out gadget cat-a-lot which also uses jQuery UI 1.9.2 autocomplete.

Here is the full description (copy):

Example URL:

Steps to reproduce the problem:
1. Go to
2. Click "Notify this user" in the sidebar
3. Start typing in the "Select the template to be added to the user's page..." text-input

What is the expected behavior?
- jQuery UI dialog widget does not disappear, dropdown on top of the dialog widget.

What went wrong?,eoXHwJK

- jQuery UI dialog widget disappears (though inputs are still accessible)
- some parts are still visible so it really looks like something went wrong with rendering

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? No Opera Next 23.0

Chrome version: 35.0.1916.153 m  Channel: stable
OS Version: 6.1 (Windows 7)
Flash Version: Shockwave Flash 14.0 r0

- When I display:none the #AjaxUmContainer, the outer container becomes visible again.
- Mozilla Firefox (latest RC) and Internet Explorer 11 do not have this issue.
- It became an issue after update to jQuery UI 1.9.2 from  1.8.24
- I am using an ATI Radeon HD 7500G video card.
- Use if you want to have pretty JS code

Tracked this further down: It appear to be
<span role="status" aria-live="polite" class="ui-helper-hidden-accessible">58 results are available, use up and down arrow keys to navigate.</span>

which has set css to

position:absolute; left:-99999999px;

Changing to

position:absolute; left:-9999999px;

solves the issue. Blink should gracefully handle this:
"4.3.8 Unsupported Values

If a UA does not support a particular value, it should ignore that value when parsing style sheets, as if that value was an illegal value."
Comment 2 Rainer Rillke @commons.wikimedia 2014-06-28 10:37:41 UTC
Literally all occurrences of jquery.ui.autocomplete are affected. I think it should be fixed in core.
Comment 3 Andre Klapper 2014-06-30 15:28:42 UTC
Created attachment 15783 [details]
Screenshot from Google Chrome 35

Rainer: Thanks for the great quality bug report and analysis.

Workaround in Google Chrome 35 is to press "Esc" key when browser content is focused.

No problem in Firefox 30, dropdown just goes away and screen not blackened.
Comment 4 Andre Klapper 2014-06-30 15:45:18 UTC
Trevor, Timo: ping

Wondering how much impact this has and in how many places (popular gadgets etc) we use jQuery UI 1.9.2 autocomplete, and whether there's something we could fix on our side.
Comment 5 Krinkle 2014-06-30 16:07:49 UTC
Is there an upstream jQuery bug report?

I don't think it's worth investigating this from our end. Duplicative effort and rather inefficient as I don't think any of us are familiar enough with the internals of the jQuery UI library itself. We can pull in patches from upstream as they come available.

I expect either jQuery UI will make a minor release with a work-around, or Chrome will address their recent regression and roll it out on their end.
Comment 6 Rainer Rillke @commons.wikimedia 2014-07-01 15:46:51 UTC
(In reply to Krinkle from comment #5)
> Is there an upstream jQuery bug report?
Not needed. The issue is home-made:

Going to submit a patch.
Comment 7 Krinkle 2014-07-01 15:49:18 UTC
Ah, right. Yeah, that should probably be updated to match the latest value from the rule it was forked from:

> .ui-helper-hidden-accessible { position: absolute !important; clip: rect(1px 1px 1px 1px); clip: rect(1px,1px,1px,1px); }
Comment 8 Gerrit Notification Bot 2014-07-01 16:11:12 UTC
Change 143337 had a related patch set uploaded by Rillke:
Update rule for vector styled .ui-helper-hidden-accessible
Comment 9 Gerrit Notification Bot 2014-07-01 19:03:28 UTC
Change 143337 merged by jenkins-bot:
vector/jquery.ui.core.css: Update rule for .ui-helper-hidden-accessible
Comment 10 Gerrit Notification Bot 2014-07-01 19:04:06 UTC
Change 143377 had a related patch set uploaded by Bartosz Dziewoński:
vector/jquery.ui.core.css: Update rule for .ui-helper-hidden-accessible
Comment 11 Gerrit Notification Bot 2014-07-01 19:04:50 UTC
Change 143379 had a related patch set uploaded by Bartosz Dziewoński:
vector/jquery.ui.core.css: Update rule for .ui-helper-hidden-accessible
Comment 12 Gerrit Notification Bot 2014-07-01 19:12:46 UTC
Change 143377 merged by Ori.livneh:
vector/jquery.ui.core.css: Update rule for .ui-helper-hidden-accessible
Comment 13 Gerrit Notification Bot 2014-07-01 19:12:55 UTC
Change 143379 merged by Ori.livneh:
vector/jquery.ui.core.css: Update rule for .ui-helper-hidden-accessible
Comment 14 Bartosz Dziewoński 2014-07-01 19:17:59 UTC
Fixed by Rillke's patch, deployed by Ori.
Comment 15 Andre Klapper 2014-10-07 21:33:26 UTC
[Backport was merged into 1.24wmf10 and 1.24wmf11 once upon a time, hence setting Backport_WMF flag to +]

Note You need to log in before you can comment on or make changes to this bug.