builds: current os: all there is an additional browser buster link neede within "Debug", it should set mozilla into a non-warn state, so that no popups arise encountering non-reachable domains, that would make random-browser-busting testing much more usable
Assignee: asa → chofmann
this would really streach deeper into the client and how it responds to http connection requests and content, not browser buster. gagan might know if this is just prefs we can set or if additional work can be made to no pop error dialogs..
I don't know of a pref that can do that. HTTP/Networking does not itself popup the errors-- it propogates them thru the interface provided by the client. The best way might just be in docshell/webshell area. Rick what do you think about this?
there are already bugs asking for these things, if i were awake i could find them. one would put error messages in the sidebar, another might put them in the js console. ideally they amount to writing a new implementation of some error handling thing.
QA Contact: doronr → timeless
proposing mozilla1.1, that would enable us testing mozilla with the yahoo random list for days, weeks... maybe we need can report uptime statistics to netcraft then :)
Assignee: chofmann → general
QA Contact: timeless → general
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Nobody around these days knows what a "browser buster" is. Closing this bug due to the incomprehensible comments.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
In its time Browser Buster was the Cadillac of automated QA testing allowing a single person to find bugs that previously took a whole army of QA testers to uncover ;-) but as you say, no need for this bug now.
You need to log in before you can comment on or make changes to this bug.