Object.observe() oh yes!
Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
21–30 of 37 posts
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#22I like the Template element, but what I'd really like is a way to escape out of JavaScript and html directly to my JavaScript views. That'd be more convenient than splitting client side view development across the JavaScript logic and html templates that reside somewhere else. Plus, I think that'd offer caching benefits vs. having to send templates across the wire every time.
You want AngularJS
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#23Is anybody else's Chrome on Mac crashing frequently? I'd like them to fix that first. Also, the whole no Flash on Linux thing.
Word. EDIT: chrome has flash on linux, last i checked. are you using your package manager's version of chromium?
Nope, google-chrome.
I found a fix shortly after I posted this comment.
They fixed in v24 (but mine isn't upgrading automatically, even after restart from v22). So instead, I followed this:
http://productforums.google.com/d/msg/chrome/PEgELQH5zcg/c5l...
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#24Is anybody else's Chrome on Mac crashing frequently? I'd like them to fix that first. Also, the whole no Flash on Linux thing.
Yes, started about a week ago, crashes (but Mac OS doesn't seem to detect it as a crash), I'm not using any plugins, etc...
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#25Is anybody else's Chrome on Mac crashing frequently? I'd like them to fix that first. Also, the whole no Flash on Linux thing.
Yes, started about a week ago, crashes (but Mac OS doesn't seem to detect it as a crash), I'm not using any plugins, etc...
I have exactly the same issue, I've not found anyone else experiencing it and it's actually quite hard to google for ;)
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#26Earlier quoted context omitted.
There's definitely a mindset on Chrome that: - any feature, no matter how small, has some cost (code size, testing, cognitive complexity, etc), and frequently contributes in some way to making the product and/or other development slower. - as a developer, user, product manager etc, it's up to you to figure out how to convince other people your change is a good idea, and how your change will be maintained going forwar…
It probably is a good idea to get the code "out of sight", yes, but "deleting the code from the repo altogether" still seems a bit odd to me. I guess I'm too used to DCVSes with light feature branching--I would expect every piece of code to end up in your codebase as a result of a merge commit, and be backed out by backing out that merge commit--leaving the unmerged feature branch itself available indefinitely if any…
It's not really deleting the code since it's still there in version history. You can always revert the revert to get a similar effect.
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#27Does this break Meteor.js? (It uses for.. templates)
Seems like it shouldn't, since it appears to require invoking JS code to use the templates.
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#28This would be a lot more exciting if there were a way to insert data dynamically like Handlebars, Mustache, etc.
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#29Earlier quoted context omitted.
Yes, started about a week ago, crashes (but Mac OS doesn't seem to detect it as a crash), I'm not using any plugins, etc...
I have exactly the same issue, I've not found anyone else experiencing it and it's actually quite hard to google for ;)
Oh... yay? Now I know I'm not alone! It happens quite frequently.
Re: Chrome 26 Beta: Template Element and Unprefixed CSS Transitions
#30Earlier quoted context omitted.
Why does it kill the emotion? With yepnope (and other libs) you can do conditional loading and only use the JS shims on IE8 while the other always-green browsers use the awesome stuff.
I know, and it's awesome but I'd like to just say "Cool! Now I can use this awesome technology and forget about the 100 JS alternatives for doing the same thing", but I still cannot forget about those ;(
that's your job. deal with it. or don't.