Closed
Bug 739038
Opened 13 years ago
Closed 13 years ago
Window.print() causes weird issues, making Fennec unusable
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox15 verified, blocking-fennec1.0 +)
VERIFIED
FIXED
Firefox 14
People
(Reporter: martijn.martijn, Assigned: mbrubeck)
References
()
Details
(Keywords: testcase)
Attachments
(3 files)
203 bytes,
text/html
|
Details | |
1.82 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
3.07 KB,
patch
|
jst
:
review+
|
Details | Diff | Splinter Review |
Similar bugs, bug 735237 and bug 707385.
See testcase, when visiting that testcase, window.print() is invoked. After that, Fennec behaves weird. You can't navigate to any page anymore, basically.
Tested on the Galaxy Nexus, Android 4.0.2.
Updated•13 years ago
|
blocking-fennec1.0: --- → ?
Updated•13 years ago
|
Assignee: nobody → wjohnston
blocking-fennec1.0: ? → +
Updated•13 years ago
|
Assignee: wjohnston → mbrubeck
Assignee | ||
Comment 1•13 years ago
|
||
This patch makes window.print throw an exception in Fennec, similar to the patch in bug 735237.
Note: This patch applies on top of the patch from bug 735237. (They don't depend on each other functionally; they just touch nearby lines of code.)
Attachment #614580 -
Flags: review?(jst)
Assignee | ||
Comment 2•13 years ago
|
||
Pushed to Try: https://tbpl.mozilla.org/?tree=Try&rev=339284aba55e
Status: NEW → ASSIGNED
Updated•13 years ago
|
Attachment #614580 -
Flags: review?(jst) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Target Milestone: --- → Firefox 14
Assignee | ||
Comment 4•13 years ago
|
||
Oops! I included these tests in my push to Try (comment 2), but I attached (and landed) old copies of my patches that didn't include the tests. Here are some simple mochitests for this bug and bug 735237.
Attachment #614895 -
Flags: review?(jst)
Updated•13 years ago
|
Attachment #614895 -
Flags: review?(jst) → review+
Assignee | ||
Comment 5•13 years ago
|
||
Landed tests as a follow-up:
https://hg.mozilla.org/integration/mozilla-inbound/rev/362fd0d7c8c3
Comment 6•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 7•13 years ago
|
||
Comment 8•13 years ago
|
||
2 errors are thrown when the test page is opened on the latest Nightly:
E/GeckoConsole(25117): [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must to be declared in the document or in the transfer protocol." {file: "https://bug511883.bugzilla.mozilla.org/attachment.cgi?id=395841" line: 0}]
E/GeckoConsole(25117): [JavaScript Error: "NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIDOMWindow.print]" {file: "data:text/html;charset=utf-8,%3Cscript%3Ewindow.print%28%29%3B%3C/script%3E" line: 1}]
Since both are expected, I will close this bug as verified fixed on:
Firefox 15.0a1 (2012-05-30)
Device: Galaxy Nexus
OS: Android 4.0.2
Status: RESOLVED → VERIFIED
status-firefox15:
--- → verified
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•