|
|
Post by Simon Crowley on Jun 14, 2005 9:23:58 GMT -5
Download Statusbar behaves erratically with Firefox 1.1 (Deer Park) Alpha builds—issuing the command to clear finished downloads only removes half of the remaining downloads—and EZNav does not work at all. As I use these features continually while browsing, it's rather sad that they're no longer available to me.
Is there any plan to update them for Fx 1.1?
|
|
|
|
Post by Devon J on Jun 14, 2005 11:49:03 GMT -5
I'm working on a new version of dlsb with new features and compatibility with ff1.1. I'm aware of the "clear finished downloads" problem. The progress bars don't work correctly because of this bug: bugzilla.mozilla.org/show_bug.cgi?id=296335The plan is to have everything ready about the same time that ff1.1 comes out (or hopefully a little before) I wasn't aware that eznav broke. Thanks for letting me know. |
|
|
|
Post by Simon Crowley on Jun 14, 2005 12:00:26 GMT -5
Ah, excellent! Thank you for the prompt reply. :)
|
|
|
|
Post by thingy van Leeuwen on Jul 14, 2005 7:43:06 GMT -5
Somehow this message came in another thread? I wanted to place it here
I have changed the content of chrome.manifest
This file is in the directory: extensions\{EF5CF93A-0DFF-49dd-B098-956626B354E5}\
content eznav jar:chrome/eznav.jar!/content/eznav/
overlay chrome://browser/content/browser.xul chrome://eznav/content/eznavoverlay.xul
(2 lines: content and overlay)
and then it seems to be working again.
Of course this has to be changed in the xpi file but until an update is available you can try this.
thingy
|
|
|
|
Post by Devon J on Jul 14, 2005 19:48:11 GMT -5
Hmm, firefox 1.1 is supposed to automatically convert any existing contents.rdf (old format) into a proper chrome.manifest (new format)
|
|
|
|
Post by thingy on Jul 15, 2005 2:40:39 GMT -5
On my computer Deer Park created this file:
overlay chrome://browser/content/browser.xul chrome://eznav/content/eznavoverlay.xul
content EZNav jar:chrome/eznav.jar!/content/eznav/
Also the maxVersion needs to changed to <em:maxVersion>1.0+</em:maxVersion>
|
|
|
|
Post by thingy on Jul 15, 2005 15:20:04 GMT -5
I just did a further test and it seems that changing the line chrome:name="EZNav" to chrome:name="eznav" in the contents.rdf file solves the problem and changing the maxVersion value to 1.0+ in install.rdf
Maybe you can confirm that and post a new version so that others can use the extension with DP
|
|
|
|
Post by Devon J on Jul 15, 2005 16:33:22 GMT -5
Interesting, thanks for looking into that. I'm in the process of updating all my extensions, but it might take a little while. In general, I'm not worried about supporting alpha releases.
|
|
