Why do Chromium-based browsers mess up an Angular app?

Question

Angular

Hello! Why do Chromium-based browsers mess up an Angular app?
The fox sees, even the Donkey sees .... the rest do not stick in what needs to be done.
The bottom line is that the application works, but I have many blocks hidden and by clicking on the radiobutton, I get the ng-show block. It seems that everyone who is on Chromium does not understand how to read ng-show, ng-hide, ng-click, etc.
What the hell? All work in the pipe ((((
For example, in the code you can see how FF processed:

<div style="display: none;" class="panel panel-primary show-block" ng-show="showBlock">Тут содержимое блока</div>

those. he added style="display: none;"
What Chrome did:

<div class="panel panel-primary show-block" ng-show="showBlock">Тут содержимое блока</div>

those. he does not care that initially it should be display: none; because worth ng-show

Answer 1

Chrome has nothing to do with it. Your application gives an error somewhere and does not start, so ng-show does not work.