Can you demonstrate it in a plunker or similar? I'm not having any trouble with Chrome 33 and manipulating classes in directives.
Have you debugged your directive to see where it fails? What kind of error are you seeing other than that it just doesn't work? On Saturday, March 1, 2014 4:19:45 AM UTC-7, Robin Hoover wrote: > > Chrome 33, all platforms. > > Simple set-up: AngularJS can easily change the DOM, such as writing a CSS > class to an element depending on certain conditions. This should be done > with what's called a directive. > > Big Problem: Chrome 33 is denying this simple ability to AngularJS. The > simple Javascript can be found here : > https://github.com/rhoover/rhoover.github.io/blob/master/scripts/6b8958af.scripts.js > > This background directive was working, it no longer is!! > > Same mis-behavior across multiple sites, multiple computers, multiple > platforms (Linux, Mac, Windows, but not Chrome for Android), multiple > versions of AngularJS. > > Cross posted here in case it's totally a Chrome bug: > https://productforums.google.com/forum/#!category-topic/chrome/report-a-problem-and-get-troubleshooting-help/windows7/33-Beta/UzAoyAL9xS0 > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
