I get this errors in the Java Console of the Smart Client
ERROR - Debug - Error at css parsing, tgs_mat_2,null:Found a dimension where a comma or a { was expected at line 26. Skipping ruleset.
ERROR - Debug - Error at css parsing, tgs_mat_2,null:Found a dimension where a comma or a { was expected at line 38. Skipping ruleset.
ERROR - Debug - Error at css parsing, tgs_mat_2,null:Found a dimension where a comma or a { was expected at line 112. Skipping ruleset.
ERROR - Debug - Error at css parsing, tgs_mat_2,null:Found a dimension where a comma or a { was expected at line 124. Skipping ruleset.
but don’t understand why?
This is how my style looks like:
[attachment=0]css_1.png[/attachment]
[attachment=1]css_2.png[/attachment]
how else can that work if i have a css with a a . on my website. and that is used by an american (where the . is the decimal point) and by a dutch guy (where the , is the decimal point)
that will then never work… Or you should have to supply 2 different css sheets based on the locale of the browser…
Also having .5 margin i guess that only makes sense to me recently with the high resolution screens (especially mobile) because if it would really be a pixel then a pixel can’t be divided…
But i guess if a pixel in css is really 4 hardware pixels on the screen then a half is possible…
A pixel is not always a pixel as the user can zoom out. And if you divide a div that is 50 pixels wide into four sections you are into fractional pixels whether you intended to or not (one of the gotchas of responsive design). So half pixel values in CSS are fairly common, especially for margins. High density displays and browsers being capable of sub pixel rendering now just means it’s happening all the time.