Note that there are some explanatory texts on larger screens.

plurals
  1. POAngularjs - IE8 in IE7 modus (and in IE8 compatibility modus) not working properly
    primarykey
    data
    text
    <p>I'm having a little problem with Angularjs version 1.0.1. I created an app and tested it in IE8 in IE7 modus and it is not listening to ng-change nor ng-click, didn't test other handles but at least those two don't work for me... (<strong>all other browsers are just fine</strong>) I hope you guys can help me with this, or maybe I'm missing something here... Is there a special treatment for IE7/8?</p> <p>Here you see the controller:</p> <pre><code>CalculatorCtrl = function($scope) { $scope.btw = 1; $scope.input = 0.00; $scope.output = 0.00; $scope.getBedrag = function() { var input = $scope.input; var btw = $scope.btw; var output = 0.0; if(input != 0) { input = parseFloat(input.replace (",", ".")); var tmp = input+""; $scope.input = tmp.replace(".", ","); } if($scope.isNumber(input)) { output = $scope.calculateBedrag(input); if(btw == 1) output = output * 1.19; $scope.output = output.toFixed(2).replace('.', ','); } else { //alert('Voer een bedrag in a.u.b.'); $scope.input = 0; $scope.output = 0; } } } </code></pre> <p>In the html I simply use:</p> <pre><code>&lt;input autocomplete="off" ng-model="input" class="x-width" type="text" name="bedrag" value="" ng-change="getBedrag()" /&gt; &lt;input class="x-width" disabled="disabled" type="text" name="bedrag" value="{{output}}" /&gt; </code></pre> <p>Hope someone can help me :)</p> <p><strong>Edit:</strong> Wel I tried IE Tester to in IE7 modus, didn't work either. I don't have any machine with <em>real</em> IE7 on it, so I can't test that...</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload