I actually think this is a really interesting, key area of current web development, how about we add some links to resources putting either argument forward?
On Tue, Jul 20, 2010 at 3:30 PM, Phil Archer <ph...@w3.org> wrote: > I must offer a contrary view to Edward! > > Any page that requires a user with normal vision to have to zoom on any > device is, in my view, a sign of a really badly designed page on a really > smart device. > > Pixels can be regarded as a proportional measure since pixel density varies > between screens. Ems are proportional to the size of text you're using - and > that's generally the thing you want to be proportional to. > > For me, line thickness can justifiably given in pixels (and that's mainly > because 'thin' means 1px in the standards browsers and a different measure, > 2px, in you-know-which browser). Image sizes should always be specified in > the markup, so that's in pixel sizes too. Apart from that, it's ems all the > way for me. > > Phil. > > Edward Lynn wrote: > >> Modern browsers now implement page zoom, and so using ems for me is >> becoming >> unnecessary. I get much better x-browser control with px's and so that is >> the direction im moving in >> >> Ed >> >> On Tue, Jul 20, 2010 at 2:53 PM, <agerasimc...@unioncentral.com> wrote: >> >> Hi, >>> >>> I've been converting some of our company public-facing static web-sites >>> from pixels to ems for layout and font-size. >>> But just recently I encountered several references that pixels are >>> getting >>> back into popularity - "as it offers absolute control over text", and >>> that >>> most browsers now can resize font based on pixels. >>> >>> Any thoughts/suggestions on whether I should push the effort on >>> converting >>> our sites to ems? >>> >>> Anya Gerasimchuk >>> >>> >>> ******* >>> This message may contain confidential information intended only >>> for the use of the addressee(s) named above and may contain >>> information that is legally privileged. If you are not the >>> addressee, or the person responsible for delivering it to the >>> addressee, you are hereby notified that reading, disseminating, >>> distributing or copying this message is strictly prohibited. If you >>> have received this message by mistake, please immediately notify >>> us by replying to the message and delete the original message >>> immediately thereafter. Thank you. >>> ******* >>> >>> >>> ******************************************************************* >>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >>> Help: memberh...@webstandardsgroup.org >>> ******************************************************************* >>> >> >> >> ******************************************************************* >> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >> Help: memberh...@webstandardsgroup.org >> ******************************************************************* >> > > -- > > > Phil Archer > W3C Mobile Web Initiative > http://www.w3.org/Mobile > > http://philarcher.org > @philarcher1 > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: memberh...@webstandardsgroup.org > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
