Bug 1752307 Comment 16 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
And the hits keep coming. Happened after I changed an event that fired off this morning @ 9AM to tomorrow @ 5PM. The same event that fired off @ 9AM (that I just moved to tomorrow popped up once again). The fix for this issue either caused or is now a byproduct and is now causing 1765995.

Error console gave em this.

10:20:58.959 [Exception... "Component returned failure code: 0x805e0006 (NS_ERROR_CONTENT_BLOCKED) [nsIChannel.asyncOpen]"  nsresult: "0x805e0006 (NS_ERROR_CONTENT_BLOCKED)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: load :: line 191"  data: no] FaviconLoader.jsm:191:20
    load resource:///modules/FaviconLoader.jsm:191
    load resource:///modules/FaviconLoader.jsm:581
    loadIcons resource:///modules/FaviconLoader.jsm:659
    iconTask resource:///modules/FaviconLoader.jsm:635
    _runTask resource://gre/modules/DeferredTask.jsm:344
    _timerCallback resource://gre/modules/DeferredTask.jsm:315
    _timerCallback resource://gre/modules/DeferredTask.jsm:334
    callback resource://gre/modules/DeferredTask.jsm:189

10:21:41.824 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:194
    observe resource://gre/modules/LoginManagerChild.jsm:194
    handleEnter chrome://global/content/elements/autocomplete-input.js:580
    addressInputOnBeforeHandleKeyDown chrome://messenger/content/messengercompose/addressingWidgetOverlay.js:765
    onBeforeHandleKeyDown chrome://messenger/content/messengercompose/MsgComposeCommands.js:4534
    handleKeyDown chrome://global/content/elements/autocomplete-input.js:474
    AutocompleteInput chrome://global/content/elements/autocomplete-input.js:40
Revision 1 by
on 
And the hits keep coming. Happened after I changed an event that fired off this morning @ 9AM to tomorrow @ 5PM. The same event that fired off @ 9AM (that I just moved to tomorrow popped up once again). The fix for this issue either caused or is now a byproduct and is now causing 1765995.

Error console gave me this.

10:20:58.959 [Exception... "Component returned failure code: 0x805e0006 (NS_ERROR_CONTENT_BLOCKED) [nsIChannel.asyncOpen]"  nsresult: "0x805e0006 (NS_ERROR_CONTENT_BLOCKED)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: load :: line 191"  data: no] FaviconLoader.jsm:191:20
    load resource:///modules/FaviconLoader.jsm:191
    load resource:///modules/FaviconLoader.jsm:581
    loadIcons resource:///modules/FaviconLoader.jsm:659
    iconTask resource:///modules/FaviconLoader.jsm:635
    _runTask resource://gre/modules/DeferredTask.jsm:344
    _timerCallback resource://gre/modules/DeferredTask.jsm:315
    _timerCallback resource://gre/modules/DeferredTask.jsm:334
    callback resource://gre/modules/DeferredTask.jsm:189

10:21:41.824 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:194
    observe resource://gre/modules/LoginManagerChild.jsm:194
    handleEnter chrome://global/content/elements/autocomplete-input.js:580
    addressInputOnBeforeHandleKeyDown chrome://messenger/content/messengercompose/addressingWidgetOverlay.js:765
    onBeforeHandleKeyDown chrome://messenger/content/messengercompose/MsgComposeCommands.js:4534
    handleKeyDown chrome://global/content/elements/autocomplete-input.js:474
    AutocompleteInput chrome://global/content/elements/autocomplete-input.js:40

Back to Bug 1752307 Comment 16