We're looking for a user researcher to understand the needs of developers and designers. Is this you or someone you know? Check out the post: https://mzl.la/2IGzdXS


Web content compatibility

Jump to:

While the introduction of multi-process capabilities to Firefox should be seamless and invisible to Web content, there are some exceptions and subtle changes from past behavior. This article discusses the known differences you may encounter.


Here you'll find information about events whose behaviors have changed due to multiprocess Firefox's implementation.

No bubbling of events from <option> to <select>

Historically, Firefox has allowed keyboard and mouse events to bubble up from the <option> element to the parent <select> element. This doesn't happen in Chrome, however, although this behavior is inconsistent across many browsers. For better Web compatibility (and for technical reasons), when Firefox is in multi-process mode and the <select> element is displayed as a drop-down list. This behavior is unchanged if the <select> is presented inline and it has either the multiple attribute defined or a size attribute set to more than 1.

Rather than watching <option> elements for events, you should watch for {event("change")}} events on <select>. See bug 1090602 for details.

See also

Document Tags and Contributors

Contributors to this page: rolfedh, Sheppy
Last updated by: rolfedh,