Print status bar dialog sometimes persists across multiple fuzzing iterations
Categories
(Core :: Fuzzing, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
Details
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #1697963 +++
I guess another description could be "window.print() does not always block".
I don't have a test case for this but I've seen it a few times now.
I'm running with prefs:
print.always_print_silent=true
print.print_to_file=true
print.print_to_filename='/dev/null'
print.show_print_progress=true
Required results:
window.print()
is called and script execution is blocked while print is in progress (print progress bar is shown if pref enabled).
Actual results:
window.print()
is called and script execution continue while the print is in progress. Test cases continue to run and close. This will break sync with the framework if a call to window.print()
causes a failure before it is complete but after the test case has been closed.
I'm not sure what the best way forward here is since this seems like the correct functionality for an end user.
Should we make window.print()
block on fuzzing builds or add a pref?
Should we add an additional fuzzing only function to FuzzingFunctions?
Any other ideas? I think I prefer the pref option.
Assignee | ||
Comment 1•3 years ago
|
||
Let me know if this doesn't work for your purposes.
Updated•3 years ago
|
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2a5153831f8b Add a pref for window.print to block. r=tsmith
Comment 3•3 years ago
|
||
bugherder |
Description
•