-----Original Message----- From: Sam Brown [mailto:freejack_in...@yahoo.com] >You can use the DOM object to get at settings such as deviceXDPI and others. I've used it to determine a client's DPI and set different styles to correct for IE rounding errors at higher DPI. http://www.w3schools.com/htmldom/dom_obj_screen.asp
It's nice to know that theoretically, it's possible to get the DPI. I just tried via the deviceXDPI and logicalXDPI and it returned "undefined." Actually, the only thing that JS could determine was my resolution and color/pixel depth. Switching to IE gave 96 dpi which is not right. From: Felix Miata [mailto:mrma...@earthlink.net] >Not the monitor's actual DPI, but the DPI actually applied to the viewport, assuming a compliant browser with JS enabled: http://fm.no-ip.com/auth/dpi-screen-window.html http://fm.no-ip.com/auth/Font/fonts-ptdemo.html I checked both of those and neither told me my DPI. One showed me a picture and said 'if this box isn't 1" then your DPI is not properly set.' I guess FireFox isn't a compliant browser. When I use IE it give me 96 dpi which is not correct since the 1" box is not 1". So, is coding based off of incorrect data any better than ignoring the data altogether? Personally, I try to make my job easier and not more difficult. And worrying about a measurement that likely is incorrect and largely irrelevant is not making my life easier. Mike ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
