• Skip to main content
  • Skip to primary sidebar
  • Home
  • News
  • Windows 11
  • Firefox
  • Chrome
  • Microsoft Edge
  • Android

Techdows

Latest Technology News

Plugin Hang UI Now available on Firefox 20 Aurora and Nightly Builds

Last updated on February 16, 2013 By Venkat

We’ve reviewed Firefox 20 Aurora in the past which currently available for download and brings new features to the table like Downloads panel, separate per-window private browsing and Plugin hang UI (for Windows only) to terminate hanging plugin like Flash. This UI to control hanging plugins has been landed on latest Aurora and nightly builds and available for testing.

Firefox 20 Aurora gives Control to user in killing hanging plugins

What’s use of Plugin Hang UI for user?

FYI Firefox automatically kills hanging plugin after waiting for 45 seconds thanks to Out of Process Plugins (OOPP) or crash protection offered for browser, during this time period Firefox may become unresponsive and user has no control over flash plugin that is hanging the browser.

Mozilla has created UI for hanging plugins so that whenever a plugin hangs (currently works for Flash only) UI for that plugin will be shown to user which he can end by clicking “stop plugin”, so that he doesn’t need to wait till the browser to become responsive again.

Firefox-plugin-hang-UI-dialog-box

At present Firefox may not produce UI when plugin hangs, this feature still needs some improvement before presented to users in release channel.

Let me tell you when you use this feature Mozilla will receive telemetry data about UI’s usage patterns which allows them to make adjustments to make UI more consistently appear to user when plugin hangs. [Via]

What do you think of this feature? useful or not?share with us in comments.

Filed Under: Firefox, News Tagged With: Firefox 20, Firefox 21, Plugin Hang Ui, plugins

Primary Sidebar

Connect with us

Twitter; Facebook; YouTube;

Recent Posts

  • Solving the ChatGPT Network Error in Step by Step Guidelines
  • How to Fix 9Anime Error 500 in 6 Steps
  • Solving “xcrun: error: invalid active developer path” in Git on MacOS

Important Site links

  • About
  • Advertise
  • Contact
  • Privacy Policy

Copyright © 2023 Techdows.com