Title: dropdowns – Make WordPress Core --- # Tag Archives: dropdowns [ ](https://profiles.wordpress.org/helen/) [Helen Hou-Sandi](https://profiles.wordpress.org/helen/) 6:18 am _on_ October 10, 2014 Tags: [4.1 ( 40 )](https://make.wordpress.org/core/tag/4-1/), dropdowns, [plugins ( 33 )](https://make.wordpress.org/core/tag/plugins/)    # 󠀁[Scalable Dropdowns update](https://make.wordpress.org/core/2014/10/10/scalable-dropdowns-update/)󠁿 In our initial meeting on Wednesday ([IRC log](https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2014-10-08&sort=asc#m936665)), we outlined some steps and a fairly aggressive timeline to get ourselves in a place where changes to wp_dropdown_users() ([#19867](https://core.trac.wordpress.org/ticket/19867)) and wp_dropdown_pages() ([#9864](https://core.trac.wordpress.org/ticket/9864)) are suitable for patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. review. To that end, we’ve opened a handful of [issues on GitHub](https://github.com/helenhousandi/wp-19867-9864/issues) for work and discussion, so that we can track completion. These tasks include evaluating various accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology( for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) areas (touch, mobile, keyboard, screen reader), creating a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. wrapper, UIUI User interface skinning, and page hierarchy representation. Please check them out and participate as you are able and willing. Let’s keep those issues task-oriented, however – any other questions or comments can go here. [#4-1](https://make.wordpress.org/core/tag/4-1/), [#dropdowns](https://make.wordpress.org/core/tag/dropdowns/), [#plugins](https://make.wordpress.org/core/tag/plugins/) [ ](https://profiles.wordpress.org/helen/) [Helen Hou-Sandi](https://profiles.wordpress.org/helen/) 2:53 am _on_ October 8, 2014 Tags: [4.1 ( 40 )](https://make.wordpress.org/core/tag/4-1/), dropdowns, [plugins ( 33 )](https://make.wordpress.org/core/tag/plugins/)    # 󠀁[Scalable Dropdowns and More, chat on 2014/10/8](https://make.wordpress.org/core/2014/10/08/scalable-dropdowns-and-more-chat-on-2014108/)󠁿 In 3.9, I started taking a look at solving some long-standing scaling issues with dropdowns, notably those for users ([#19867](https://core.trac.wordpress.org/ticket/19867)) and pages ([#9864](https://core.trac.wordpress.org/ticket/9864)). I arrived at a conclusion about our mixed usage of autocomplete and autosuggest far too late to make it for 3.9, and did not add it to my plate for 4.0, but would like to tackle it again for 4.1. We can solve these issues smartly by using a combination of Ajax-powered autocomplete/ suggest and smart defaults, e.g. users with the most content pre-loaded for quick access without having to run a search. As a brief overview of where I see us going with this – a roadmap, if you will: user dropdown, page dropdown, current instances of jQuery UIUI User interface autocomplete (multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site** users and new site), tags/nonhierarchical taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies). UI, more built-in taxonomy UIs ([#14877](https://core.trac.wordpress.org/ticket/14877)), and possibly more as we discover appropriate places. Not all of this will happen in 4.1 – think of this as not only a solution to long-standing, painful problems, but also a step in a series of many. To that end, we will be holding an initial chat at [19:00 UTC on 2014/10/8](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20141008T1900) to get things moving. [@ericlewis](https://profiles.wordpress.org/ericlewis/) and I have begun early development as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. – for more, see [this particular branch](https://github.com/helenhousandi/wp-19867-9864/tree/select2-19867), which experiments with using Select 2 as a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. helper library for the UI. [#4-1](https://make.wordpress.org/core/tag/4-1/), [#dropdowns](https://make.wordpress.org/core/tag/dropdowns/), [#plugins](https://make.wordpress.org/core/tag/plugins/)