Closed Bug 1589982 Opened 5 years ago Closed 4 years ago

GeckoView test will fail when DocumentChannel is enabled.

Categories

(GeckoView :: General, defect, P3)

Unspecified
All
defect

Tracking

(Fission Milestone:Future, firefox71 wontfix, firefox72 affected)

RESOLVED WORKSFORME
Fission Milestone Future
Tracking Status
firefox71 --- wontfix
firefox72 --- affected

People

(Reporter: jya, Assigned: snorp)

References

Details

See https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=272011843&repo=try&lineNumber=2546

The GV unit test expects a set amount of events to occur.

However, when using DocumentChannel nsIWebProgressListener will emit an extra event when redirecting to the real channel.

Either the tests need to be amended, or change the java binding so that redirects shouldn't be forwarded.

I think this code [1] should be checking for STATE_IS_DOCUMENT as well as STATE_START/STOP flags, so that we only forward the actual document start/stop, and not intermediate ones for redirects.

[1] https://searchfox.org/mozilla-central/rev/d7537a9cd2974efa45141d974e5fc7c727f1a78f/mobile/android/modules/geckoview/GeckoViewProgress.jsm#244

P3 Fission bug

Priority: -- → P3

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?

Matt, do you need to fix this GeckoView test in 72 if you plan to ship DocumentChannel for non-Fission?

Fission Milestone: ? → M5
Flags: needinfo?(matt.woodrow)

No, DocumentChannel is only enabled for desktop currently, so it won't block anything until we want to support GV.

Flags: needinfo?(matt.woodrow)
Assignee: nobody → snorp

GV bugs don't need to block Fission MVP.

Fission Milestone: M5 → Future
Depends on: 1620875
Blocks: 1626250
Blocks: 1605382

We have DocumentChannel enabled already, so this isn't a problem anymore.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.