Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #28510 > unrolled thread

Chrome 44 mobile-web-app-capable

Back to article view | Back to comp.lang.javascript

Contents

  Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-09 11:54 +0800
    Re: Chrome 44  mobile-web-app-capable "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2015-08-09 10:06 +0200
      Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-09 16:57 +0800
        Re: Chrome 44  mobile-web-app-capable "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2015-08-09 11:10 +0200
    Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-09 16:54 +0800
      Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-12 19:32 +0800
        Re: Chrome 44  mobile-web-app-capable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-08-12 15:44 +0100
          Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-13 15:22 +0800
          Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-14 07:19 +0800
            Re: Chrome 44  mobile-web-app-capable Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-08-14 00:36 +0100
              Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-15 08:40 +0800
                Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-15 09:02 +0800
                  Re: Chrome 44  mobile-web-app-capable Richard Maher <maher_rjSPAMLESS@hotmail.com> - 2015-08-15 09:10 +0800

#28510 — Chrome 44 mobile-web-app-capable

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?

[toc] | [next] | [standalone]

#28511

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)

[toc] | [prev] | [next] | [standalone]

#28513

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?

[toc] | [prev] | [next] | [standalone]

#28514

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)

[toc] | [prev] | [next] | [standalone]

#28512

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.

[toc] | [prev] | [next] | [standalone]

#28518

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.

[toc] | [prev] | [next] | [standalone]

#28520

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.

[toc] | [prev] | [next] | [standalone]

#28523

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.

[toc] | [prev] | [next] | [standalone]

#28526

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?

[toc] | [prev] | [next] | [standalone]

#28527

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.

[toc] | [prev] | [next] | [standalone]

#28529

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?

[toc] | [prev] | [next] | [standalone]

#28530

Disbelief! I think it's the protocol???

http:// seems to work and httpS:// seems to fail. Which are you using Ben?

Aargh, I just worked out it's probably just complaining about a dicky 
certificate on our test server? Is the latest version of Chrome 
stricter? Some Certificate Authorities deprecated?

I want to die.

[toc] | [prev] | [next] | [standalone]

#28531

On 8/15/2015 9:02 AM, Richard Maher wrote:
> Disbelief! I think it's the protocol???
>
> http:// seems to work and httpS:// seems to fail. Which are you using Ben?
>
> Aargh, I just worked out it's probably just complaining about a dicky
> certificate on our test server? Is the latest version of Chrome
> stricter? Some Certificate Authorities deprecated?
>
> I want to die.
Yep, I can't see the wood for the trees :-(

Chrome's complaining about a SHA-1 certificate being in there somewhere 
which is why it wants to display the URL.

Pilot error, sorry!

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web