Thanks John, It's not such a huge problem, for me - seems like the fix is a lot of a time sink ;) I can fix the errors I'm seeing by deleting the live bookmarks that are trying to refresh and failing because the sites no longer exist.
I usually only have sites open that I'm working on in the my dev browser. Hence why I use two browsers on purpose (lastpass & xmarks make this simple) I'll just add a 3rd (portable FF) if I need another instance of a browser so I can login to the same website with different credentials, instead of using my dev one. :) On Feb 19, 3:13 am, John J Barton <[email protected]> wrote: > On Feb 18, 1:32 am, cheekybuddha <[email protected]> wrote: > > > > "Livemark Service: feed processor received an invalid channel > > > for ...." > > > i also get this message but I always thought it was because I had Sage > > RSS list open in the sidebar and firebug considered it part of the > > same tab. > > There are two reasons the errors end up in the Console. First I broke > errors.js in Firebug in some way so it works less well now than it did > in 1.4. Second, errors.js gets its information from nsIConsoleService > in firefox which mixes errors from all parts of Firefox. > > I'm not going to work on the first problem, but I will help anyone who > wants to take it on. Fundamentally the problem is that we need a > comprehensive test suite to figure out how to sort out the errors, a > test suite that includes errors from HTML, CSS, JS in the same and > different web pages and in all the places extensions can run code. > I've tried to fix errors.js without a test suite and one fix breaks > something else. > > I'll try to look into the second problem but it's not at the top of > the list now. > > I know this is unsatisfactory but I just do not see another solution. > > jjb > > jjb > > > > > > > d -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
