Closed Bug 595896 Opened 14 years ago Closed 14 years ago

Test to make sure that snippets appear in about:home

Categories

(Firefox :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- final+

People

(Reporter: ehsan.akhgari, Assigned: mak)

References

Details

(Whiteboard: [test in bug 598264][about-home])

STR:

1. Load about:home.
2. Look at the error console:

Error: uncaught exception: [Exception... "Security error"  code: "1000" nsresult: "0x805303e8 (NS_ERROR_DOM_SECURITY_ERR)"  location: "chrome://browser/content/aboutHome.js Line: 144"]

Which is coming from here: <http://mxr.mozilla.org/mozilla-central/source/browser/base/content/aboutHome.js#144>.  This suggests that updating the snippets on this page is broken, and it indeed is (I don't see any snippets at all).  This should probably block.

Also, as far as I can see, this page was landed without tests, which, I think, is odd...
blocking2.0: --- → ?
that should be fixed in today's nightly
Fixed by https://hg.mozilla.org/mozilla-central/rev/84ee6bc0484d .

We should get a test that _some_ snippet appears (at least the default).
Assignee: nobody → mak77
blocking2.0: ? → beta6+
Flags: in-testsuite?
OS: Mac OS X → All
Hardware: x86 → All
Target Milestone: --- → Firefox 4.0b6
Either mark this fixed and file a followup for the test, or morph this into being about the test, please?
blocking2.0: beta6+ → final+
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Morphed to cover the test.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: Snippet update on about:home is broken → Test to make sure that snippets appear in about:home
Target Milestone: Firefox 4.0b6 → ---
I have a general test in bug 598264.
Whiteboard: [test in bug 598264]
there is a test now, pushed with bug 598264.
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Flags: in-testsuite? → in-testsuite+
Resolution: --- → FIXED
Whiteboard: [test in bug 598264] → [test in bug 598264][about-home]
You need to log in before you can comment on or make changes to this bug.