Hi all,
I've been working on a draft specification for a creating a dedicated
cross-browser external protocol launching standard based on the behavior of
msLaunchUri in Internet Explorer.
The draft is here:
http://bengjohnson.github.io/ExternalProtocolSpecification.html
I'm looking for
On 3/30/14 8:02 PM, ext Jungkee Song wrote:
I think the related testing efforts [1] (the current status [2]) from
many industry players (of course Anne contributed enormous part of the
test too) are improving the Web in a way.
Yes, I agree, and thanks to all that contribute to this effort.
After working with developers inside and outside Microsoft, it seems there are
several types of paste that make sense in various scenarios. For instance,
1- if pasting into a rich document, it could be important to maintain source
styling information.
2- When pasting into a wiki from an
Would this be similar to the Web Intents spec proposal that Google was
championing (based on Android Intents)?
Sincerely,
James Greene
On Thu, Mar 27, 2014 at 5:52 PM, Ben Johnson ben.john...@citrix.com wrote:
Hi all,
I’ve been working on a draft specification for a creating a
Thanks, fixed in https://dvcs.w3.org/hg/IndexedDB/rev/9cbb21363f41
On Sun, Mar 30, 2014 at 10:22 PM, Zhang, Zhiqiang
zhiqiang.zh...@intel.comwrote:
3.1.7 Transaction
enum IDBTransactionMode {
readonly,
readwrite,
versionchange
};
Hi,
let me introduce my Custom Element scenario: an interactive map element,
powered by one of the well-known JS APIs (such as Google Maps API or so).
Typically, the markup will be like
my-map lat=... lon=... zoom=... controls
However, the underlying JS needs to know when this element's
Hi!
I think the biggest difference is that web intents work between web pages,
whereas this is used to launch installed programs on the user’s computer.
Think about this use case: A web page with a list of ssh hosts. When you
click on a link, the JS on the page calls
I certainly support some kind of per-element media query, or resize event,
if the well-known performance issues around these ideas can be resolved,
but otherwise Custom Elements don't have a lot to say about this problem.
Typically, when using a plain JS API (and not a custom declarative
Kosta has pretty much covered it. Web Intents as well as current browser
implementations are heavily geared towards web-based protocol handling,
potentially at the expense of external handlers.
The final question in my initial e-mail Should it be better aligned with
web-based protocol
OK. Thanks for the clarifications, Konstantin Ben!
Sincerely,
James Greene
On Mon, Mar 31, 2014 at 12:55 PM, Ben Johnson ben.john...@citrix.comwrote:
Kosta has pretty much covered it. Web Intents as well as current browser
implementations are heavily geared towards web-based protocol
On Mar 31, 2014, at 8:20 PM, Ondřej Žára ondrej.z...@firma.seznam.cz wrote:
Hi,
let me introduce my Custom Element scenario: an interactive map element,
powered by one of the well-known JS APIs (such as Google Maps API or so).
Typically, the markup will be like
my-map lat=...
11 matches
Mail list logo