Chrome updates - breaks shit.
-
Our EHR which is a browser only based EHR contantly breaks when Chrome does updates.
Anyone else use web apps that break all the time because of browser updates?
Sadly - as a total non developer, I have no idea if this is Chrome just changing shit that requires devs to constantly update their site/apps to work with Chrome OR the apps themselves are just that poorly written that they break when Chrome updates OR my app dev is using such rare stuff in Chrome that that rare stuff is constantly being removed, etc, etc.
It's a constant battle.
In fact it's so bad that the EHR company is making their own Chromium based "desktop app" that won't be updated unless the vendor wants to update it. I suppose as long as this 'app' is really locked down and nothing else can invoke it to take advantages of discovered Chromium flaws, then this might be a doable setup. The app can also be locked down (by the vendor) to only be used to access the EHR system, making it less of an issue being updated less frequently.
Thoughts, opinions, etc?
-
@Dashrender said in Chrome updates - breaks shit.:
Anyone else use web apps that break all the time because of browser updates?
Generally, but certainly not always, that means a browser update has exposed an existing flaw, rather than breaking a working application.
-
@Dashrender said in Chrome updates - breaks shit.:
In fact it's so bad that the EHR company is making their own Chromium based "desktop app" that won't be updated unless the vendor wants to update it.
Read: The EHR is so bad, that they require systems not being standard or patched to be functional!
-
@Dashrender said in Chrome updates - breaks shit.:
Thoughts, opinions, etc?
Unprofessional and a blatant attempt to circumvent HIPAA requirements on patch security.
-
@scottalanmiller said in Chrome updates - breaks shit.:
@Dashrender said in Chrome updates - breaks shit.:
In fact it's so bad that the EHR company is making their own Chromium based "desktop app" that won't be updated unless the vendor wants to update it.
Read: The EHR is so bad, that they require systems not being standard or patched to be functional!
I have a very hard time not disagreeing with this.
you don't see MS making a new browser just for O365 because Chrome keeps breaking shit. and anyone who wants to give me shit over the new Chromium based Edge - just shut it.
-
@Dashrender said in Chrome updates - breaks shit.:
you don't see MS making a new browser just for O365 because Chrome keeps breaking shit. and anyone who wants to give me shit over the new Chromium based Edge - just shut it.
Exactly. In fact, they dropped Edge and are moving full on to Chrome officially, not just as a recommendation.
No serious software is having this issue. This is not in any way a Chrome problem.
-
@scottalanmiller said in Chrome updates - breaks shit.:
@Dashrender said in Chrome updates - breaks shit.:
you don't see MS making a new browser just for O365 because Chrome keeps breaking shit. and anyone who wants to give me shit over the new Chromium based Edge - just shut it.
Exactly. In fact, they dropped Edge and are moving full on to Chrome officially, not just as a recommendation.
No serious software is having this issue. This is not in any way a Chrome problem.
Chrome clearly has/does and will continue to make updates that breaks things - but not as a general rule.
The Chromium project recently announced the retirement of some feature that would basically kill ad-block addons. After the extension makers/consumers complaints about this, they changed their minds.
-
Chrome isn't breaking anything. A Chrome update does not change the EHR code, causing it to break. Chrome updates only change Chrome code, and it's to patch security flaws, performance fixes, etc... The fact that EHR stops working correctly is on the EHR software, not Chrome. So no, Chrome breaks nothing. It's the EHR that is broken. Stop saying Chrome updates break things. That's not the case.
-
@Dashrender said in Chrome updates - breaks shit.:
Chrome clearly has/does and will continue to make updates that breaks things - but not as a general rule.
They CAN do that, but do you have any reason to believe that they have done that? You say that they clearly have, but I'm certainly not aware of that. "Clearly" is clearly not a good term here.
-
@Dashrender said in Chrome updates - breaks shit.:
Our EHR which is a browser only based EHR contantly breaks when Chrome does updates.
Anyone else use web apps that break all the time because of browser updates?
Sadly - as a total non developer, I have no idea if this is Chrome just changing shit that requires devs to constantly update their site/apps to work with Chrome OR the apps themselves are just that poorly written that they break when Chrome updates OR my app dev is using such rare stuff in Chrome that that rare stuff is constantly being removed, etc, etc.
It's a constant battle.
In fact it's so bad that the EHR company is making their own Chromium based "desktop app" that won't be updated unless the vendor wants to update it. I suppose as long as this 'app' is really locked down and nothing else can invoke it to take advantages of discovered Chromium flaws, then this might be a doable setup. The app can also be locked down (by the vendor) to only be used to access the EHR system, making it less of an issue being updated less frequently.
Thoughts, opinions, etc?
We suffered same issue we had Bahmni EMR, and Google chrome change log was lacking serverly with stuff like
many bugs fixes and enhacnemntsWe suffered from issues due to under the hood change many times, like the ability to make only 6 connections to SSL https socket thing
You dont need Chromuim app, just use this
https://chromium.woolyss.com/Or run linux and saltstack and run command to upgrade chrome when it is tested . Thats what we did . sadly we didnt manage moving all to Linux cause of the dam MS Office.
ALso run some users or yourself on the Chrome BEta, to catch issues prior
-
@Dashrender said in Chrome updates - breaks shit.:
The Chromium project recently announced the retirement of some feature that would basically kill ad-block addons. After the extension makers/consumers complaints about this, they changed their minds.
Which is not related for several reasons...
- We are talking web apps using the Chrome browser platform, ad-ons are fat software that works with, not in, the browser. Those are totally different things and don't apply to this conversation.
- Chome did not break them, it gave them warning, they failed to change, and still Chrome decided to not update so that they would keep working.
You are giving examples of how this is not something Chrome does.
-
@scottalanmiller said in Chrome updates - breaks shit.:
@Dashrender said in Chrome updates - breaks shit.:
The Chromium project recently announced the retirement of some feature that would basically kill ad-block addons. After the extension makers/consumers complaints about this, they changed their minds.
Which is not related for several reasons...
- We are talking web apps using the Chrome browser platform, ad-ons are fat software that works with, not in, the browser. Those are totally different things and don't apply to this conversation.
- Chome did not break them, it gave them warning, they failed to change, and still Chrome decided to not update so that they would keep working.
You are giving examples of how this is not something Chrome does.
Also Chromium is not Chrome.
-
@scottalanmiller said in Chrome updates - breaks shit.:
@Dashrender said in Chrome updates - breaks shit.:
The Chromium project recently announced the retirement of some feature that would basically kill ad-block addons. After the extension makers/consumers complaints about this, they changed their minds.
Which is not related for several reasons...
- We are talking web apps using the Chrome browser platform, ad-ons are fat software that works with, not in, the browser. Those are totally different things and don't apply to this conversation.
- Chome did not break them, it gave them warning, they failed to change, and still Chrome decided to not update so that they would keep working.
You are giving examples of how this is not something Chrome does.
Yes I know this this was an example of something not being broken because they declared an intention before just doing it.
But there have been past things (likely to long ago to find easily) where a great many sites were broken by an update that Chrome made. Now sure - you could say ALL those sites did something wrong and Chrome exposed that wrong thing - but you could see it from the other POV, that this was an accepted method, until Chrome change it, which suddenly made it unacceptable/broken.
-
@Dashrender said in Chrome updates - breaks shit.:
But there have been past things (likely to long ago to find easily) where a great many sites were broken by an update that Chrome made. Now sure - you could say ALL those sites did something wrong and Chrome exposed that wrong thing - but you could see it from the other POV, that this was an accepted method, until Chrome change it, which suddenly made it unacceptable/broken.
Except only one view is correct. I can't say which one is without digging into a specific example and showing if a bug was fixed, or created. But I'm not aware of this ever happening. Do you have any examples?
Sites do break all of the time. So does any software that is ghost ship or heading towards ghost ship. Software is a living thing and being unmaintained is the same as being broken.
-
@Emad-R said in Chrome updates - breaks shit.:
@Dashrender said in Chrome updates - breaks shit.:
Our EHR which is a browser only based EHR contantly breaks when Chrome does updates.
Anyone else use web apps that break all the time because of browser updates?
Sadly - as a total non developer, I have no idea if this is Chrome just changing shit that requires devs to constantly update their site/apps to work with Chrome OR the apps themselves are just that poorly written that they break when Chrome updates OR my app dev is using such rare stuff in Chrome that that rare stuff is constantly being removed, etc, etc.
It's a constant battle.
In fact it's so bad that the EHR company is making their own Chromium based "desktop app" that won't be updated unless the vendor wants to update it. I suppose as long as this 'app' is really locked down and nothing else can invoke it to take advantages of discovered Chromium flaws, then this might be a doable setup. The app can also be locked down (by the vendor) to only be used to access the EHR system, making it less of an issue being updated less frequently.
Thoughts, opinions, etc?
We suffered same issue we had Bahmni EMR, and Google chrome change log was lacking serverly with stuff like
many bugs fixes and enhacnemntsWe suffered from issues due to under the hood change many times, like the ability to make only 6 connections to SSL https socket thing
You dont need Chromuim app, just use this
https://chromium.woolyss.com/Or run linux and saltstack and run command to upgrade chrome when it is tested . Thats what we did . sadly we didnt manage moving all to Linux cause of the dam MS Office.
ALso run some users or yourself on the Chrome BEta, to catch issues prior
Except that the spec for this (RFC2616) should actually be 2. The fact that the browsers let you have six ignores the spec. This page lists all modern browsers at 6.
XHR Polling is obviously abused and most solutions should be updated to websockets.
-
Use FireFox ESR??
-
@jt1001001 said in Chrome updates - breaks shit.:
Use FireFox ESR??
The vendor specifically checks for the browser and disables use on anything they don't approve.
-
@Dashrender said in Chrome updates - breaks shit.:
@jt1001001 said in Chrome updates - breaks shit.:
Use FireFox ESR??
The vendor specifically checks for the browser and disables use on anything they don't approve.
More evidence of who is responsible for breaks.
-
@Dashrender said in Chrome updates - breaks shit.:
@jt1001001 said in Chrome updates - breaks shit.:
Use FireFox ESR??
The vendor specifically checks for the browser and disables use on anything they don't approve.
Damn, that's some Internet Explorer type nonsense right there.
-
@Dashrender said in Chrome updates - breaks shit.:
Chrome clearly has/does and will continue to make updates that breaks things - but not as a general rule.
Chrome isn't breaking things though, they are finding and resolving security/stability issues when they update. They don't update to disable things on purpose.
