622009 - Opening new tab causes funny focus behavior [caused by DivX HiQ]

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: DivX, defect)

Description

[Henry Hartley]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: DivX HiQ 2.1.0.900 on Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13

Sometimes, with "When I open a link in a new tab, switch to it immediately" NOT
checked, ctrl-left-clicking a link opens the new tab and changes focus. If
ctrl-left-clicking in the right-most open tab, I'm switched to the newly open
tab despite the setting saying not to. If on any other open tab, the new tab is
opened and I'm switched to the tab one to the right of the current tab.

I've toggled the "When I open a link in a new tab, switch to it immediately"
and in the other setting (On), it seems to work as expected. Then turning it
back off causes the behavior to go back to the above.

Disabling the DivX HiQ 2.1.0.900 extension causes behavior to return to the expected behavior. Enabling it causes the behavior noted here.

Reproducible: Sometimes

Steps to Reproduce:
1. Install and enable the DivX HiQ extension
2. Four tabs open. 
3. Ctrl-left-click on a link in the second tab from the left.

Actual Results:  
Focus moves from tab two to tab three and the new tab is opened between that
tab (three) and tab four.


Expected Results:  
New tab should open between tabs two and three and focus should remain on tab
two.


I have only seen this one this one machine so it may be very
version, OS, or hardware specific. This is my only 64-bit Windows machine, so I
really don't know.

Comment 1

[Vitaliy]

I'd like to addon to this. Please add this plugin to blocklist. On a new Firefox 4, I disabled all plugins, and addons, and Firefox worked smoothly. When I enabled "DivX HiQ 2.1.0.900" I open the first tab smoothly. The second tab sometimes works, sometimes don't. The third tab just freezes, while Firefox still responds.
If anybody from Firefox team would like it, I could even post a video proving it.

So my request is to simply put this on blocklist.

Comment 2

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.