bumped version to 0.4.1
Prevent showing more than one notification at a time.
Checking for "live bookmarks loading..." notification
--
Karl Dearden
w: http://interclue.com/
e: ka...@interclue.com
bugger, I thought I'd solved that one with the last build.
Can you just confirm for me you're using 0.4.1 (tools|addons| should say
version number next to the addon name)?
It's a difficult bug to re-create as it relies on the notification being
sent before the download is complete.
Cheers
Karl
Joe Solomon wrote:
> Second the thumbs up!
>
> On Tue, Oct 7, 2008 at 10:01 AM, Dietrich Ayala <auto...@gmail.com>
> wrote:
>
>> fantastic, looks great karl!
>>
>> On Mon, Oct 6, 2008 at 11:29 PM, karl <ka...@interclue.com> wrote:
>>>
>>> Feeds dialog will now be displayed on install and on update
>>> (whenever the version number changes).
>>>
>>> bumped version to 0.4.1
>>>
>>> Prevent showing more than one notification at a time.
>>>
>>> Checking for "live bookmarks loading..." notification
>>>
>>>
>>> -- Karl Dearden w: http://interclue.com/ e: ka...@interclue.com
>>>
>
> >
>
>
>
> ------------------------------------------------------------------------
>
>
Karl Dearden
w: http://interclue.com/
e: ka...@interclue.com
now, will only alert for the most recent feed item, and no alerts at
all for the first minute after startup. karl, can you review the
changes?
All looks good so far.
I'm interested in your use of "let" in overlay.js
--
let Cc = Components.classes;
let Ci = Components.interfaces;
--
According to the writeup at
http://developer.mozilla.org/En/New_in_JavaScript_1.7
{{{
var x = 'global';
let x = 42;
document.write(this.x + "<br>\n");
//The output displayed by this code will display "global", not "42"
}}}
So, correct me if I'm wrong here, if another add-on was loaded before
obamafox, and that addon contained the code
{{{
var Cc = null; //or anything other than Components.classes
}}}
in a global scope (as ours is).
Then this would break obamafox as soon as we tried to use the Cc
variable. Because the "var Cc" overrides the "let Cc" even though "let
Cc" is declared later in the code.
Now this all depends on how the add-on scripts are loaded (Of which I'm
not entirely certain).
I'd be interested to know what made you choose "let" here rather than
"var". What advantages to we get?
Cheers,
--
Karl Dearden
w: http://interclue.com/
e: ka...@interclue.com
Cc and Ci are already defined in the browser scope that extension code
is executed in. Using |let| here ensures that they're defined for our
use, without conflicting with the previously defined variables/consts
with those names. That said, yeah it's imprecise at best. Actually,
given that the extension only works in Firefox 3, could probably be
removed altogether, so I'll just do that.
-d