* Alex Russell wrote:
So you've written off the massive coordination costs of adding a uniform to
all code across all of Google and, on that basis, have suggested there
isn't really a problem? ISTM that it would be a multi-month (year?) project
to go patch every project in google3 and then wait
Hi all,
I’d like to propose one solution for
[Shadow]: Specify imperative API for node distribution
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18429
because select content attribute doesn’t satisfy the needs of framework/library
authors to support conditionals in their templates,
and
On Feb 14, 2014, at 7:16 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 2/14/14 10:07 PM, Ryosuke Niwa wrote:
We most vigorously object to making the CSS style resolver depend on JS
DOM object properties.
Ryosuke, I think you misunderstood the proposal. I'm pretty sure we all
object to
Hi,
I've been thinking more about selection, and I think we need a flag/switch to
indicate whether we want a isolated selection or not
since it's highly desirable to have a separate selection for creating custom
form controls like input, text area,
Any thoughts?
- R. Niwa
On Sat, Feb 15, 2014 at 1:57 AM, Maciej Stachowiak m...@apple.com wrote:
On Feb 14, 2014, at 9:00 AM, Erik Arvidsson a...@chromium.org wrote:
On Thu, Feb 13, 2014 at 9:00 PM, Maciej Stachowiak m...@apple.com wrote:
On Feb 13, 2014, at 4:01 PM, Alex Russell slightly...@google.com
On Sat, Feb 15, 2014 at 4:57 PM, Ryosuke Niwa rn...@apple.com wrote:
Hi all,
I’d like to propose one solution for
[Shadow]: Specify imperative API for node distribution
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18429
because select content attribute doesn’t satisfy the needs of
On Sat, Feb 15, 2014 at 5:56 AM, Marcos Caceres w...@marcosc.com wrote:
tl;dr: I strongly agree (and data below shows) that installable web apps
without offline capabilities are essentially useless.
Things currently specified in the manifest are supposed to help make these
apps less useless
