[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.javascript

Chrome 44 mobile-web-app-capable

Richard Maher

8/9/2015 3:54:00 AM

Does anyone here know why Chrome Web Apps show the URL since upgrading
to 44 even though mobile-web-app-capable is set to true?
12 Answers

Evertjan.

8/9/2015 8:06:00 AM

0

Richard Maher <maher_rjSPAMLESS@hotmail.com> wrote on 09 Aug 2015 in
comp.lang.javascript:

> Does anyone here know why Chrome Web Apps show the URL since upgrading
> to 44 even though mobile-web-app-capable is set to true?

I there a Javascript-related Q here?

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

Richard Maher

8/9/2015 8:55:00 AM

0

On 8/9/2015 11:54 AM, Richard Maher wrote:
> Does anyone here know why Chrome Web Apps show the URL since upgrading
> to 44 even though mobile-web-app-capable is set to true?

"display": "standalone"

In the manifest makes no difference either.

Richard Maher

8/9/2015 8:58:00 AM

0

On 8/9/2015 4:06 PM, Evertjan. wrote:
>
> I there a Javascript-related Q here?
>
Exactly which part of "Fuck off and die you stupid Cloggy" are you
struggling with?

Evertjan.

8/9/2015 9:10:00 AM

0

Richard Maher <maher_rjSPAMLESS@hotmail.com> wrote on 09 Aug 2015 in
comp.lang.javascript:

> On 8/9/2015 4:06 PM, Evertjan. wrote:
>>
>> I there a Javascript-related Q here?
>>
> Exactly which part of "Fuck off and die you stupid Cloggy"

No, it means:

Is your Q on topic or not?

> are you struggling with?

That is called projection.

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

Richard Maher

8/12/2015 11:33:00 AM

0


For those playing along at home: -

manifest.json :-

{
"short_name": "Test Fred",
"name": "Fred testing Web App",
"icons": [
{
"src": "icon1.png",
"sizes": "128x128",
"type": "image/png"
}
],
"display" : "fullscreen"
}

fred.html: -

<!DOCTYPE HTML>
<html>
<head>
<title>Fred Test</title>
<meta name = "mobile-web-app-capable" content = "yes" />
<meta name = "viewport" content = "width=device-width,
user-scalable=no, initial-scale=1, minimum-scale=1, maximum-scale=1" />

<link rel="shortcut icon" sizes="128x128" href="icon1.png" />
<link rel="apple-touch-icon" href="icon1.png" />
<link rel="apple-touch-icon" sizes="128x128" href="icon1.png" />

<link rel="manifest" href="manifest.json">
</head>

<body style="color:white;background-color:black;font-size:20px;">
<div>Hello Fred</div>
</body>
</html>

Save something as "icon1.png".

Bring up fred.html in your Android Chrome browser and "save to
homescreen". Go to your homescreen, click your icon, see if the url is
visible.

Ben Bacarisse

8/12/2015 2:44:00 PM

0

Richard Maher <maher_rjSPAMLESS@hotmail.com> writes:

> For those playing along at home: -
>
> manifest.json :-
>
> {
> "short_name": "Test Fred",
> "name": "Fred testing Web App",
> "icons": [
> {
> "src": "icon1.png",
> "sizes": "128x128",
> "type": "image/png"
> }
> ],
> "display" : "fullscreen"
> }
>
> fred.html: -
>
> <!DOCTYPE HTML>
> <html>
> <head>
> <title>Fred Test</title>
> <meta name = "mobile-web-app-capable" content = "yes" />
> <meta name = "viewport" content = "width=device-width,
> user-scalable=no, initial-scale=1, minimum-scale=1, maximum-scale=1"
> />
>
> <link rel="shortcut icon" sizes="128x128" href="icon1.png" />
> <link rel="apple-touch-icon" href="icon1.png" />
> <link rel="apple-touch-icon" sizes="128x128" href="icon1.png" />
>
> <link rel="manifest" href="manifest.json">
> </head>
>
> <body style="color:white;background-color:black;font-size:20px;">
> <div>Hello Fred</div>
> </body>
> </html>
>
> Save something as "icon1.png".
>
> Bring up fred.html in your Android Chrome browser and "save to
> homescreen". Go to your homescreen, click your icon, see if the url is
> visible.

No URL visible on my Nexus 5 running Chrome 44.0.2403.133.

--
Ben.

Richard Maher

8/13/2015 7:22:00 AM

0

On 8/12/2015 10:44 PM, Ben Bacarisse wrote:
>
> No URL visible on my Nexus 5 running Chrome 44.0.2403.133.
>
Thanks Ben! At the moment FRED has no URL present on my Samsung Galaxy
either. The problem is, the last 2 times I got it to work I changed the
last thing I did to see if it failed (which it did) change it back again
and it still failed

Sounds like Caching but I've powered off, re-homescreened etc. Last time
I added "permissions": ["fullscreen"]} and that seemed to help then fail.

The good news is with > 1 client working it looks like it IS code
dependent and not something dodgy in the way Chrome homescreens?

Strangest thing.

Richard Maher

8/13/2015 11:19:00 PM

0

On 8/12/2015 10:44 PM, Ben Bacarisse wrote:
>
> No URL visible on my Nexus 5 running Chrome 44.0.2403.133.
>
Be, (anyone) when it's displaying sans-URL can you please
Delete from homecsreen
Clear from History
Reboot phone
Go back into Chrome
Add to homescreen

and see if it still works?

Ben Bacarisse

8/13/2015 11:37:00 PM

0

Richard Maher <maher_rjSPAMLESS@hotmail.com> writes:

> On 8/12/2015 10:44 PM, Ben Bacarisse wrote:
>>
>> No URL visible on my Nexus 5 running Chrome 44.0.2403.133.
>>
> Be, (anyone) when it's displaying sans-URL can you please
> Delete from homecsreen
> Clear from History
> Reboot phone
> Go back into Chrome
> Add to homescreen
>
> and see if it still works?

Yes -- no URL shown.

--
Ben.

Richard Maher

8/15/2015 12:40:00 AM

0

On 8/14/2015 7:36 AM, Ben Bacarisse wrote:
> Richard Maher <maher_rjSPAMLESS@hotmail.com> writes:
>
>> On 8/12/2015 10:44 PM, Ben Bacarisse wrote:
>>>
>>> No URL visible on my Nexus 5 running Chrome 44.0.2403.133.
>>>
>> Be, (anyone) when it's displaying sans-URL can you please
>> Delete from homecsreen
>> Clear from History
>> Reboot phone
>> Go back into Chrome
>> Add to homescreen
>>
>> and see if it still works?
>
> Yes -- no URL shown.
>
Thanks again Ben. This is doing my head in :-(

You have Nexus 5 running Chrome 44.0.2403.133.

I have a Samsung Galaxy S5 running: -
Chrome 44.0.2403.133
Andrioid 5.0.0
Model SM-G9001 BUILD/LRX21T
Blink 537.36

and it doesn't work. I also have a friend with a Galaxy S4 that now
works. A Tablet is a Samsung gt-n8000 running 4.2.2. fails and anothe
Nexus phone that fails.

I have successful and failing cases being served by the same we-server/code.

The failing cases only show up one browser task and not a Chrome + "Web
App" tasks. I believe this is a failure to launch problem.

Remember Chrome had the problem when KitKat first came out that unless
you already had Chrome running a Web App would not launch as a Web App?

Can anyone else get this code to fail please?