forked from AuroraMiddleware/gtk
0f42d37f8b
The parser got its chars mixed up while parsing numbers like 2.3e-04. While it is unlikely to meet such numbers in human-generated css, we do have them e.g. when saving render node trees with transforms. Also add some css parser tests for number parsing.
32 lines
197 B
CSS
32 lines
197 B
CSS
a {
|
|
-gtk-dpi: 0;
|
|
}
|
|
|
|
b {
|
|
-gtk-dpi: 100;
|
|
}
|
|
|
|
c {
|
|
-gtk-dpi: -39;
|
|
}
|
|
|
|
d {
|
|
-gtk-dpi: 0.5;
|
|
}
|
|
|
|
e {
|
|
-gtk-dpi: 2.6e2;
|
|
}
|
|
|
|
f {
|
|
-gtk-dpi: 2.6E20;
|
|
}
|
|
|
|
g {
|
|
-gtk-dpi: 5e-1;
|
|
}
|
|
|
|
h {
|
|
-gtk-dpi: 2E-19;
|
|
}
|