429922 - File launch after update

Status: RESOLVED DUPLICATE of bug 491947

(Toolkit :: Application Update, defect)

Description

[abe.gillespie]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

This is a pretty insignificant bug, but I know you guys take QC seriously, so ...

This happens right after an update and before the browser has been opened again to show the update window.  If, in this scenario, you launch a local HTML file (double-click in Windows Explorer) you'll get a cryptic error message.  The nice thing is FF still loads the file despite the error.

Reproducible: Always

Steps to Reproduce:
1. Wait for a Firefox update
2. Shutdown browser after update but do not reopen
3. Double-click a local HTML file
Actual Results:  
Error message.

Expected Results:  
No error message.

Smurfy

Comment 1

[[:Cww]]

Can you give the text of the error message?  It could be a javascript alert from one of the pages you had open before you updated.  (After updates, Firefox restores your session automatically.)

Comment 2

[abe.gillespie]

Unfortunately I'd have to wait for another FF update to reproduce it (and that's even if I remember to try this again).  I can tell you with a high degree of certainty that it is not a javascript error.  Firstly, there were no pages being restored.  Secondly, the HTML file I loaded includes no Javascript.

I doubt it will, but if it helps, the local page I load is the readme.html page from famfamfam's silk icon set:  http://www.famfamfam.com/lab/icons/silk/famfamfam_silk_icons_v013.zip

Comment 3

[Wayne Mery (:wsmwk)]

abe, do you still see this problem?

Comment 4

[Robert Strong (they/them - no direct email)]

btw: this would be due to the DDE code in toolkit -> startup and not app update. We are planning on disabling DDE in bug 491947 sometime in the future which will fix this bug though it isn't the root cause hence why it shouldn't be duped to it until after bug 491947 is fixed.

Comment 5

[Robert Strong (they/them - no direct email)]

No reply to comment #3 and as stated in comment #4 this isn't an app update problem and will be fixed by bug 491947. resolving -> duplicate