[manifest] Manifest "splash_screens" with animated "any" size SVG
בע"ה
Hi,
Google recently has published icon support centered in splash screen in
Chrome 47 requiring icon minimum size 196px,
https://developers.google.com/web/updates/2015/10/splashscreen.
I propose instead "splash_screens" with animated SVG that could display
loading process similarly to almost any this days Android/iOS-native apps
like Skype, etc. Link to spec
https://w3c.github.io/manifest/#splash_screens-member
{
"src": "splashscreen.svg",
"sizes": "any"
}
Binyamin
[manifest] Manifest "background_color" with gradient?
בע"ה How about gradients in "background_color" (linear-gradient, radial-gradient, repeating-linear-gradient, repeating-radial-gradient)? Anything delays such spec/implementation? Binyamin
Re: [manifest] Manifest "sizes" fallback logic
בע"ה
Maybe lets define standard spec for it
https://github.com/w3c/manifest/issues/409, so that every browser
vendor/engine would know what is correct to do. For example lets help to
decide to pick 32x32.png or 48x48.png while requiring missing 40x40
size image.
Binyamin
On Tue, Oct 13, 2015 at 11:51 AM, Mounir Lamouri <mou...@lamouri.fr> wrote:
> Hi Binyamin,
>
> Thank you for your question.
>
> I think this behaviour should be left to the implementation there is a
> lot of UI decisions here that can't be spec'd. For example, Chrome would
> likely pick a 32x32 image when it needs a 16x16 one but might not do the
> other way around. Some UA might avoid taking a 32x32 image instead of a
> 16x16 image because one is twice as big as the other and might not be
> optimized to be seen as small. Obviously, all browsers should do a best
> effort in picking an image.
>
> -- Mounir
>
> On Mon, 12 Oct 2015, at 21:01, Binyamin wrote:
> > בע"ה
> >
> >
> > Hi,
> >
> >
> > Does "sizes" (https://w3c.github.io/manifest/#sizes-member) has any
> > fallback for device required different icon sizes?
> >
> > {
> > "icons": [
> > {
> > "src": "32x32.png",
> > "sizes": "32x32"
> > }, {
> > "src": "48x48.png",
> > "sizes": "48x48"
> > }, {
> > "src": "128x128.png",
> > "sizes": "128x128"
> > }
> > ]
> > }
> >
> > 1. For example, would device request for 16x16 return scaled down image
> > 32x32.png?
> > 2. What about request 40x40 - would it scale up 32x32.png or scale down
> > 48x48.png (40x40 is in middle of both those sizes (+8 = 48, -8 = 32))?
> > 3. Would request 96x96 use 128x128.png?
> > 4. Would request 192x192 and 512x512 use 128x128.png?
> >
> >
> >
> > Binyamin
>
Proposal - Personal Identity API
בע"ה
Hi,
I purpose to implement Personal Identity API (I have not jet found anything
similar to it).
This days all recent browsers (Chrome, Firefox, Opera, Edge, etc.) and
devices (Android, iOS, Firefox OS, etc.) prefers or requires Signin with
user personal identification data (at least email/phone).
It would be great to share/receive that data with Web "Personal Identity
API" with simple respond like
{
name: "Name",
surname: "Surname",
email: "n...@mail.com",
birth: "31/12/1999",
country: "USA"
// key: "validation-key"
}
It can very ease user identification (for Singup), maybe even
authentication for Signin (need to discuss the secure validation if any),
be used for user analytic, etc.
Currently many apps uses SSO (Single sign-on,
https://en.wikipedia.org/wiki/Single_sign-on) with different APIs and
protocols. It still requires server-side authentications.
Browsers/OSs has to validate the main personal identification data
(email/phone). Share the data after user acceptation similar to other APIs
like Geolocation API (demo http://html5demos.com/geo).
I am only wondering if it in any way could be used in save way as a Signin
authentication? Maybe by uses some encrypted validation key?
Binyamin
Re: Proposal - Personal Identity API
בע"ה
None of your mentioned techniques (WebID, FOAF+SSL, OAuth, navigator.id)
seems covering my proposal.
What I meant is simple JavaScript API to read browser/machine
logged/synchronized/identification user profile data.
For example return in Chrome
{
name: "Me",
surname: "Surname",
email: "m...@gmail.com",
birth: "31/12/1999",
country: "USA"
}
when logged/synchronized profile m...@gmail.com in Chrome (profile per
browser, etc.).
Is there any way to make it valid, safe and only-readable in a way to use
it as a "logging/identification profile" in any website?
Binyamin
On Sat, Dec 12, 2015 at 9:50 PM, Binyamin <7rai...@inbox.lv> wrote:
> בע"ה
>
> Hi,
>
> I purpose to implement Personal Identity API (I have not jet found
> anything similar to it).
>
> This days all recent browsers (Chrome, Firefox, Opera, Edge, etc.) and
> devices (Android, iOS, Firefox OS, etc.) prefers or requires Signin with
> user personal identification data (at least email/phone).
> It would be great to share/receive that data with Web "Personal Identity
> API" with simple respond like
>
> {
> name: "Name",
> surname: "Surname",
> email: "n...@mail.com",
> birth: "31/12/1999",
> country: "USA"
> // key: "validation-key"
> }
>
> It can very ease user identification (for Singup), maybe even
> authentication for Signin (need to discuss the secure validation if any),
> be used for user analytic, etc.
>
> Currently many apps uses SSO (Single sign-on,
> https://en.wikipedia.org/wiki/Single_sign-on) with different APIs and
> protocols. It still requires server-side authentications.
> Browsers/OSs has to validate the main personal identification data
> (email/phone). Share the data after user acceptation similar to other APIs
> like Geolocation API (demo http://html5demos.com/geo).
> I am only wondering if it in any way could be used in save way as a Signin
> authentication? Maybe by uses some encrypted validation key?
>
>
> Binyamin
>
