We are tracking our issues in GitHub. Maybe it makes sense filling them there
instead/as well?
We now have a ´lang´ field. I assume that is not enough?
Kenneth
-Original Message-
From: Phillips, Addison [mailto:addi...@lab126.com]
Sent: Thursday, March 19, 2015 6:32 PM
To:
Hi there,
The spec authors use GitHub for issue tracking. I duplicated your issues there:
https://github.com/w3c/manifest/issues
Thanks for looking into internationalization issues with the current spec.
Cheers,
Kenneth
-Original Message-
From: Phillips, Addison
Hi Kenneth,
Thanks for the reply.
I know you're using GitHub. However, whenever I'm filing/forwarding comments on
a document on behalf of the Working Group, I always look at the SOTD in the
document in question to see what instructions the receiving WG has. In this
case, you have a fairly
Marcos, Anssi, what do you think?
I would prefer the comments on GitHub as it seems to be a great place for
interacting with the web community, judging from our success so far.
Kenneth
-Original Message-
From: Phillips, Addison [mailto:addi...@lab126.com]
Sent: Friday, March 20,
Yes, loading components via imports today is use at your own risk since you
pull that content directly into your trust boundary. At least with script src
the platform takes measures to ensure that the imported content (the code)
can't be easily observed if it doesn't choose to be.
It seems
Ryosuke Niwa [mailto:rn...@apple.com] wrote:
Travis wrote:
2.4. I keep running into trouble when thinking about a declarative model
for web components because declarative models are based on persistent
objects in the DOM, and those persistent objects are fully mutable. In other
words, you
