1063424 - Options | Applications still shows the wrong plugin

Status: RESOLVED WORKSFORME

(Firefox :: Settings UI, defect)

Description

[Georg Fritzsche [:gfritzsche]]

(Bogdan Maris, QA [:bogdan_maris] from bug 863773, comment #28)
> I installed Foxit, Adobe, Nitro, Gaaiho and DocuCom in this order.
> Using an old Nightly (25.08.2014) I see that the newly plugin installed is
> added to Action field (one by one): https://db.tt/TFoNjZNZ
> Using latest Nightly (01.08.2014) I see that the Action field keeps the same
> plugin no matter how many plugins I install: https://db.tt/MFSJcOCa
> Opening 'Use other' will display the plugins available for opening PDF in
> the same order. This is the behavior I see before and after the fix.
> 
> Not sure If I`m testing correctly here. Comment 0 is quite confusing to me
> in order to identify the actual fix that was handled here.

([e-mail] from bug 863773, comment #29)
> I installed Adobe, Foxit, PDF-XChange and Sumatra.
> 
> Before this patch landed, the applications pane would display Sumatra as the
> alternative to the built-in viewer, while after this patch landed, the
> applications pane now displays PDF X-Change as the alternative.
> 
> If however I select Sumatra/PDF-XChange, I actually get Adobe.
> 
> Note that I tried manually applying rev 2 and that displays Adobe.

Comment 1

[Georg Fritzsche [:gfritzsche]]

Bernardo, can you take this and find out what broke here between rev 2 and 5?
Looks like the switch to mimeType.enabledPlugin.name didn't work out so well?

Comment 2

[Bernardo Rittmeyer [:rittme]]

Thank you for the help, Georg. 
Sorry about the delayed answer, I was trying to take another look at it to have a better understanding of what is happening. I will take this bug and work on it ASAP.

Comment 3

[[e-mail]]

I have no idea why but now my PDFs are now opening with the PDF X-Change plugin, which (since bug 863773 landed) is what Firefox has been claiming it was doing all along. Interestingly the Firefox that I patched with the rev 2 code also is now advertising the PDF X-Change plugin as being the one that will be used. As I am no longer able to reproduce the problem, I would be happy for this bug to be resolved worksforme.

Comment 4

[Georg Fritzsche [:gfritzsche]]

Neil, if you want you could try |touch|ing the plugin libraries between restarts to see if that breaks anything.
Otherwise i'm happy to close WFM as this seems the only bad report so far.

Comment 5

[Bernardo Rittmeyer [:rittme]]

Have you restarted the browser after the installations? 
Probably this have some effect.
Also, please note that the plugins are the "blue lego piece" at the actions list and not the applications you can use (e.g. the ones you can choose with "Use other").

Comment 6

[[e-mail]]

(In reply to Bernardo Rittmeyer from comment #5)
> Have you restarted the browser after the installations?
> Probably this have some effect.
At the time, I restarted several times so as to compare the two patches. (But that was two weeks ago and I've rebooted since then so anything could have happened.)

Comment 7

[Georg Fritzsche [:gfritzsche]]

Bodgan said on IRC that he got the correct behavior here now, so i think we can call this WFM.
Let me know if you think otherwise Bernardo?