On 2016/12/13 13:50:53, mlamouri wrote:
> What is this testing exactly? The test name says "multipleurls" but the actual
> testing seems to check that reloading reset the `defaultRequest`.
I think we test both navigation and mulitple urls in this test (we use multiple
url constructor to create defaultRequest).
whywhat
2016/12/14 02:20:39
I think that just adding a ctor test in the presen
On 2016/12/14 at 01:51:53, zhaobin wrote:
> On 2016/12/13 13:50:53, mlamouri wrote:
> > What is this testing exactly? The test name says "multipleurls" but the
actual
> > testing seems to check that reloading reset the `defaultRequest`.
>
> I think we test both navigation and mulitple urls in this test (we use
multiple url constructor to create defaultRequest).
I think that just adding a ctor test in the presentation-api.html is enough for
this change. maybe getAvailability could be tested additionally for multiple
urls case when not all of them are incompatible or that the connection created
by start() has one of the URLs from the list - but that's for the follow up cls
and maybe additional test harness built (one can mock Mojo services in
LayoutTests now, for instance).
Issue 2552343009: [Presentation API] Adds DOMString[] constructor to PresentationRequest.
(Closed)
Created 4 years ago by zhaobin
Modified 3 years, 11 months ago
Reviewers: mark a. foltz, whywhat, imcheng, mlamouri (slow - plz ping), foolip, haraken
Base URL:
Comments: 71