[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Taler] inline installation limitations / landing page
From: |
Florian Dold |
Subject: |
Re: [Taler] inline installation limitations / landing page |
Date: |
Fri, 19 Feb 2016 14:13:06 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
Actually, I was completely wrong about subdomains not being allowed.
I guess the distinction between http and https still holds, but that's
not as bad!
- Florian
On 02/19/2016 01:39 PM, Florian Dold wrote:
> Oh, and also note that there's even a difference for http or https; if
> it's configured as inline installable for the one, it won't work on the
> other.
>
> -F
>
> On 02/19/2016 01:37 PM, Florian Dold wrote:
>> Hi,
>>
>> I've managed to get inline installation [1] for the Taler WebExtension
>> Wallet to work, but there's one problem: It just works on *one* domain
>> (not even with subdomains) that is specified in the developer dashboard
>> for the application in the chrome webstore.
>>
>> It would be possible to upload the extension once per (sub)domain where
>> we want inline installation, but that's a nightmare ...
>>
>> Does anybody have thoughts on what is the best way to structure our
>> landing page(s) (demo.taler.net and test.taler.net) around that
>> limitation? Where do we want the inline installation?
>>
>> - Florian
>>
>> [1] https://developer.chrome.com/webstore/inline_installation
>>