[whatwg] Splash screen proposal for web apps ?

Laurent Perez l.laurent.p at gmail.com
Thu Aug 1 11:17:03 PDT 2013

Our user agent is a HTTP proxy, currently we are feeding it HTML5 pages,
then we are parsing custom data-* attributes and replacing them with UI
components, for example data-carousel becomes a touch carousel, and so on.

Instead of creating another data-splashscreen attribute, we always try
standards first, so I'm evaluating the widgets spec, PhoneGap went the
<feature> splashscreen way, RIM chose a <rim:splash> vendor namespace. On
top of that there is also the manifest spec, implemented by Firefox OS.

The sysapps WG is what I was looking for, thanks :)


On Thu, Aug 1, 2013 at 5:59 PM, Rich Tibbett <richt at opera.com> wrote:

> > On Wed, Jul 31, 2013 at 9:15 PM, Ian Hickson <ian at hixie.ch> wrote:
> >> On Wed, 31 Jul 2013, Laurent Perez wrote:
> >> >
> >> > Is there work going on on a Splash screen specification ?
> >>
> >> What's the use case?
> >>
> >> Generally speaking, Web pages load incrementally, so by the time you've
> >> downloaded an image, you should be able to just show the Web page
> itself,
> >> at least in a state good enough for the user. (For example, even really
> >> large and expensive pages like Google+ render in a usable state quickly,
> >> even though they continue to load assets and scripts in the background
> and
> >> thus actually don't present an interactive UI straight away.)
> On Fri, Aug 2, 2013 at 12:48 AM, Laurent Perez <l.laurent.p at gmail.com>
> wrote:
> > The use case is to show a "please wait, loading..." message until all
> > resources of an index page (js, css, html, images, fonts) are downloaded.
> > When the message dismisses, the index page is ready for a non-blocking UI
> > navigation since js was already loaded.
> >
> > We plan to implement it in our own user agent, and I was wondering if I
> > should go the Apple meta way or use the w3c widgets spec and use a webapp
> > descriptor. I know the widgets spec has been implemented by some (Opera,
> > Phonegap to describe an hybrid application), I was wondering if work was
> > still going on on the splash proposal.
> Your exact use case is unclear as to whether you want this for web
> pages in general (in which case you have the problem that you need to
> load some resources before the page itself loads) or for some kind of
> packaged web application scenario.
> For the latter, there has been some discussion around splash screens
> [1] in the context of the ongoing work around the web manifest
> specification [2].Check that out and direct your query to W3C SysApps
> [3]?
> [1] https://github.com/sysapps/sysapps/issues/41
> [2] http://manifest.sysapps.org
> [3] http://www.w3.org/2012/sysapps/

J2EE tips and best practices

More information about the whatwg mailing list