834975 - Browser support for default URL

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Browser, defect)

Description

[Carol Yang [:cyang]]

For a GCF TC like 27.22.4.26.1.1, it will launch the browser, loading the default URL. In some cases, the network simulator (Anritsu or Anite) expects the default URL to be configurable.

Question for Moz folks: It seems like the default URL is just hard-coded right now. There's no way to configure this through UI, right?

Question for Daniel: If the default URL is not configurable, can this TC be waived?

Comment 1

[Ben Francis [:benfrancis]]

There is no default URL/home page, the start page is internal to the browser.

It seems this test case can be removed.

Comment 2

[Jason Smith [:jsmith]]

This bug reads off as being invalid - should we close it?

Comment 3

[Michael Vines [:m1] [:evilmachines]]

Seems likely invalid, but would be nice to get confirmation from TEF that this won't be an issue for certification (the existing ni? request).

Comment 4

[Daniel Coloma:dcoloma]

I think this is referring to the STK default URL mentioned in bug 826547. I don't think we should allow to change through the UI to change this URL. If the GCF test is OK with current behaviour, I am also fine with it.

Comment 5

[Andrew Overholt [:overholt]]

(In reply to Daniel Coloma:dcoloma from comment #4)
> If the GCF test is OK with current behaviour, I am also fine with it.

Carol, does the GCF test specify that the default URL has to be configurable through the UI?

Comment 6

[Carol Yang [:cyang]]

(In reply to Andrew Overholt [:overholt] from comment #5)
> (In reply to Daniel Coloma:dcoloma from comment #4)
> > If the GCF test is OK with current behaviour, I am also fine with it.
> 
> Carol, does the GCF test specify that the default URL has to be configurable
> through the UI?

Andrew, the GCF test does not specify that the default URL has to be configurable through the UI. However, the default URL expected can change and does depend on who made up the test. As is with the set of tests we have, the GCF TC will fail.

If there are no plans to allow the user to change the default URL through the UI, and Daniel can confirm that this TC can be waived, then we can mark this TC as NA internally and close this bug out.

Comment 7

[Andrew Overholt [:overholt]]

> If there are no plans to allow the user to change the default URL through
> the UI, and Daniel can confirm that this TC can be waived, then we can mark
> this TC as NA internally and close this bug out.

David, can you please confirm here that you don't think this will be a problem?  (I know you provided this info during triage but I'd rather you wrote it here than me :) ).

Comment 8

[David Palomino [:dpalomino]]

Hi Andrew, 

From the carrier's point of view, there is no blocker on this issue. As per previous comments this TC in GCF can be set as not applicable, that was my main worry about this. 

Anyway, we're trying to get a list of potential "dangerous" TC for getting GCF certification. When we'll have this list, we'll revisit it and reopen if needed. 

Thanks!
David

Comment 9

[Andrew Overholt [:overholt]]

(In reply to David Palomino [:dpv] from comment #8)
> Anyway, we're trying to get a list of potential "dangerous" TC for getting
> GCF certification. When we'll have this list, we'll revisit it and reopen if
> needed. 

Great, thanks, David.  I'm going to bb- this and remove it from the dependency list of bug 808607.

Comment 10

[Ben Francis [:benfrancis]]

This is by design.