Closed
Bug 589851
Opened 14 years ago
Closed 14 years ago
[Regression] protocol handlers are broken on 8/22 nightly build
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec2.0a1+)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
fennec | 2.0a1+ | --- |
People
(Reporter: aakashd, Assigned: blassey)
References
Details
Attachments
(1 file)
717 bytes,
patch
|
dwitte
:
review+
|
Details | Diff | Splinter Review |
Build Id: Mozilla/5.0 (Android; U; Linux armv71; en-US; rv:2.0b4pre) Gecko/20100823 Namoroka/4.0b4pre Fennec/2.0a1pre Steps to Reproduce: 1. Go to lassey.us/proto.html 2. Click on "call me" Actual Results: Nothing happens. Expected Results: The phone application on the mobile device should launch (i.e. a launch application dialog should pop-up in the browser).
Reporter | ||
Updated•14 years ago
|
tracking-fennec: --- → ?
Assignee | ||
Comment 1•14 years ago
|
||
Assignee: nobody → blassey.bugs
Attachment #468392 -
Flags: review?(dwitte)
Comment 3•14 years ago
|
||
Comment on attachment 468392 [details] [diff] [review] patch r=dwitte
Attachment #468392 -
Flags: review?(dwitte) → review+
Should this patch have a test, so that it doesn't break again?
Flags: in-testsuite?
Assignee | ||
Comment 6•14 years ago
|
||
pushed to a1 rel branch: http://hg.mozilla.org/mozilla-central/rev/c4980b518c79 this still needs to land on m-c, so not closing it yet
Assignee | ||
Comment 7•14 years ago
|
||
pushed http://hg.mozilla.org/mozilla-central/rev/8baac435bd14
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•14 years ago
|
||
verified FIXED on builds: Mozilla/5.0 (X11; U; Linux armv71; Nokia N900; en-US; rv:2.0b5pre) Gecko/20100825 Namoroka/4.0b5pre Fennec/2.0a1pre and Mozilla/5.0 (Android; Linux armv71; Nokia N900; en-US; rv:2.0b5pre) Gecko/20100825 Namoroka/4.0b5pre Fennec/2.0a1pre There's litmus testcases for this that need to be updated a bit- https://litmus.mozilla.org/show_test.cgi?id=12313 https://litmus.mozilla.org/show_test.cgi?id=12335
Status: RESOLVED → VERIFIED
Flags: in-litmus?
Reporter | ||
Comment 9•14 years ago
|
||
Also, there's a follow-up bug here: https://bugzilla.mozilla.org/show_bug.cgi?id=590477
Reporter | ||
Updated•14 years ago
|
Assignee: blassey.bugs → mozaakash
Reporter | ||
Updated•14 years ago
|
Assignee: mozaakash → blassey.bugs
Flags: in-litmus? → in-litmus?(mozaakash)
Reporter | ||
Comment 10•14 years ago
|
||
wip, but here's an update. litmus testcases https://litmus.mozilla.org/show_test.cgi?id=12335 https://litmus.mozilla.org/show_test.cgi?id=12313 updated to regression test this bug. Still need to add a few more tests around this bug as well as a test html page that, so we stop using brad's page.
Can't we write an automated test for this? Seems like the "no URL handlers fire" thing would be amenable to automation.
Reporter | ||
Comment 12•14 years ago
|
||
We can take care of both, redundancy wouldn't be a bad thing here. Unit tests would be great though
Flags: in-litmus?(mozaakash) → in-litmus-
Reporter | ||
Updated•14 years ago
|
Flags: in-litmus- → in-litmus?(mozaakash)
You need to log in
before you can comment on or make changes to this bug.
Description
•