This is definitely a concern, but I think it's orthogonal to the use of Angular. Chrome does auto-update unless that's deliberately disabled, and those updates can change core JavaScript behavior (usually in the name of security) which can break functionality. Two recent examples we ran into, not in the context of an Angular app, which caused unexpected disruption for users and required significant investigation and effort to work around:
* A button on a form was making an XHR call to do something on the backend, then displaying the result in a new tab on success. The latest Chrome suddenly decided this looked like an unwanted popup (even though the user had clicked to initiate the action) and tried to block it; if you told it to allow the "popup," it would only open it thereafter in a new window, not a tab. * A locking module (Drupal) we were using to prevent multiple users from editing the same item was relying on an XHR request to release the lock when the page was unloaded. Obviously not a fully reliable mechanism, but worked well enough--until Chrome decided to disallow requests triggered by this event when you navigate away from a page (although not when closing the window/tab, for whatever reason). I've never seen any announcement or discussion of changes like this, and spent some time poring over changelogs without finding any acknowledgement of them. It's really not an ideal situation, and you might want to discuss with your IT department the possibility of disabling automatic Chrome updates. But again, this is not an Angular-specific issue. Kevin On Wed, Feb 26, 2014 at 6:18 AM, Raymond <[email protected]> wrote: > Hi All, > > We've started using Angular JS in developing a core in-house application. > We've decided to support running the web application in Google Chrome only. > We've been completely satisfied with using Angular JS as our client-side > scripting framework. But we'd like to know how future proof and reliable it > will be in terms of Google Chrome updates. My concern is the possibility of > a future Google Chrome update breaking Angular JS/UI code thus affecting > our web application. I know the same thing could be said with using another > JavaScript library and/or another browser and/or operating system. > > I was also under the impression that our company's Google Chrome updates > were controlled by an administrator. But just recently, I've seen our > Google Chrome version was updated to the latest. > > I'd be glad to hear your inputs. > > Thanks! > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
