I forgot to mention: xpfe/components/console/resources/content/consoleBindings.xml That's where at least half of the fix for this would take place.
I'd like to have module owner feedback, please, contrasting this bug to bug 228205. 228205's approach is preferable to the one I'm considering here, but not much in the way of traction. This one, with nsIIOService, could have a patch relatively quickly.
Personnally i'd like a very simple way to debug only one tab. I would open the page, open the js console and I could indicate to this console to only debug the page in question (maybe with a drop-down list with all opened tabs, selecting the page in this drop-down list would only display errors about this page in the console).
*** Bug 133565 has been marked as a duplicate of this bug. ***
Reporter: Are you sure you want something this fine-grained? How about doing what is suggested in bug 302211?
bug 302211 is about filtering the type of error, not the source of the error. I am currently using the Console2 extension: https://addons.mozilla.org/firefox/1815/ to restrict what is shown, but it only allows me a single filter term. So I can enter "foo" to only show messages from "foo.com". But, when I'm developing pages for "foo.com" and loading JS from "bar.com", I have no way to specify that I want to see messages from "foo" and "bar". I have resorted to running a separate browser so when I google for something the console doesn't get flooded.
Assignee: error-console → nobody
Product: SeaMonkey → Toolkit
QA Contact: jrgmorrison → error.console
Given the notoriously bad JS written by eg. Yahoo, not being able to filter the originator is pretty much a major annoyance!
Bug 760951 added a filter.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 760951
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.