On 9 December 2013 09:33:47 Yoav Weiss y...@yoav.ws wrote:
IMO, it might be better not to define an explicit way to inline the
manifest, and let authors simply use data URIs to do that, if they see such
a need.
e.g. link rel=manifest href=data:application/manifest+json,{ ... }
If this becomes
On Mon, 02 Dec 2013 11:42:30 -, Mounir Lamouri mou...@lamouri.fr
wrote:
Hi,
I am not sure that telling the webpage what the user is currently trying
to search is a great idea. However, if a webpage wants its own find in
page UI I guess a simple solution would be to do something similar
On Thu, 01 Aug 2013 17:57:20 +0100, Tab Atkins Jr. jackalm...@gmail.com
wrote:
HTML is the Web's serialization format *for HTML, and other text-like
things*. As Kornel's example shows, HTML is *not* well suited to
holding key/value pairs or the like;
The ugly part is current lack of support
On 1 August 2013 12:44:19 Scott Wilson scott.bradley.wil...@gmail.com wrote:
Or you could perhaps use XML. A bit like, er, this:
http://www.w3.org/TR/widgets/
Hehe ;)
I'm trying to address two things:
1. it's been shown ever and over again that developers on the wild web are
really bad at
On Mon, 15 Jul 2013 09:57:30 +0100, Jonas Sicking jo...@sicking.cc wrote:
indexeddb:origin/persistence/database/objectStore/index/key/keypath
Each piece above would have to be encoded such that it contains only
valid, non-'/', URL characters. For things like database name and
objectStore name
I'd like to propose using HTML as basis of manifest format, similar in
spirit to Web Components imports, e.g.
link rel=manifest import href=/my-app-definition.html
and then my-app-definition.html could contain link, meta or other
elements.
Rationale:
* while JSON is wonderful for
in error recovery feels like an omission in this API.
--
regards, Kornel Lesiński
and
won't work for the web.
Pusher is a popular service that provides what SSE was supposed to do, but
over Web Sockets, and their library reconnects automatically:
http://pusher.com/docs/client_api_guide/client_connect#connection-states
I think that's a good model to follow.
--
regards, Kornel
namespacing of reusable components:
jqueryui::widget
/jqueryui::widget
(not True Namespaces in the XML sense, but IMHO that's also a good thing).
If I understand correctly, serialisation of :: in XML isn't a problem,
as XML documents could use the is= attribute instead.
--
regards, Kornel Lesiński
