gtk2/testsuite/css/parser/integer.ref.css

a {
  opacity: 0;
}

b {
  opacity: 1;
}

c {
  opacity: -1;
}

d {
  opacity: 2147483647;
}

e {
  opacity: -2147483648;
}

f {
  opacity: 1;
}

i {
  opacity: 377;
}

l {
  opacity: 3;
}
tests: Add CSS integer parsing tests 2011-04-09 11:49:41 +00:00			`a {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: 0;`
tests: Add CSS integer parsing tests 2011-04-09 11:49:41 +00:00			`}`

Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`b {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: 1;`
Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`}`

			`c {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: -1;`
Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`}`

			`d {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: 2147483647;`
Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`}`

			`e {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: -2147483648;`
Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`}`

			`f {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: 1;`
Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`}`

			`i {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: 377;`
Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`}`

			`l {`
testsuite: Update integer test Make the test use an actual integer property that accepts negative numbers (opacity) instead of one that wants units (margin-top) or can't deal with negative numbers (everything else). 2019-04-11 18:45:17 +00:00			`opacity: 3;`
Update all css parser tests I have not tracked down in detail where all these changes originate, this commit just gets things back to working again. 2017-10-15 03:52:03 +00:00			`}`