Last modified: 2012-09-27 01:11:06 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 T27396, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25396 - SimpleSearch and MWSuggest are active simultaneously
SimpleSearch and MWSuggest are active simultaneously
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
1.17.x
All All
: Lowest normal (vote)
: ---
Assigned To: Trevor Parscal
http://laxstrom.name/simplesearch.png
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-03 07:28 UTC by Niklas Laxström
Modified: 2012-09-27 01:11 UTC (History)
5 users (show)

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


Attachments

Description Niklas Laxström 2010-10-03 07:28:27 UTC
See the URL for screenshot.
Comment 1 Trevor Parscal 2010-10-04 17:35:18 UTC
It's not a styling issue, it's a "you have mediawiki.legacy.mwsuggest and ext.vector.simpleSearch enabled simultaneously. Normally ext.vector.simpleSearch would disable mediawiki.legacy.mwsuggest on the client side, in a sort of hacky and silly way, and this is clearly failing.

A better solution would be to not send both suggestion systems.
Comment 2 Derk-Jan Hartman 2010-10-04 20:09:24 UTC
Sure it is mwsuggest ? Looks like field history from the browser to me. Not sure which browser this is, but I have seen such a problem with some versions of webkit, where the disabling of field suggestions/history was broken.
Comment 3 Trevor Parscal 2010-10-04 20:10:09 UTC
You know what, i think you are absolutely right! Sorry for the bad diagnosis.
Comment 4 Niklas Laxström 2010-10-04 20:37:40 UTC
The screenshot is from recent version of Chrome.
Comment 5 Derk-Jan Hartman 2010-10-11 15:10:08 UTC
@Niklas, I have seen similar issues with nightly builds of WebKit for Safari. It disappeared after several days, so I presume this issue is a bug in Chrome and of temporary nature, i doubt it can be worked around.
Comment 6 Derk-Jan Hartman 2010-10-17 18:28:18 UTC
I don't think that there is anything else we can do about this. Closing as wontfix of a fixed upstream issue.

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


Navigation
Links