Comments on: 5 Reasons Why iPhone Application Development Doesn’t Cut the Digital Mustard http://www.halobrite.com/weblog/2007/07/18/5-reasons-why-iphone-application-development-doesnt-cut-the-digital-mustard/ A weblog that aims to promote the awareness and creation of ubiquitous computing. Fri, 21 Nov 2008 08:14:03 +0000 http://wordpress.org/?v=2.2.1 By: Scott Robbin http://www.halobrite.com/weblog/2007/07/18/5-reasons-why-iphone-application-development-doesnt-cut-the-digital-mustard/#comment-5 Scott Robbin Thu, 19 Jul 2007 13:31:36 +0000 http://www.halobrite.com/weblog/2007/07/18/5-reasons-why-iphone-application-development-doesnt-cut-the-digital-mustard/#comment-5 Thanks, John. Great explanation. The article has been updated to reflect a lack of fixed positioning only. Thanks, John. Great explanation. The article has been updated to reflect a lack of fixed positioning only.

]]> By: John Allsopp http://www.halobrite.com/weblog/2007/07/18/5-reasons-why-iphone-application-development-doesnt-cut-the-digital-mustard/#comment-4 John Allsopp Thu, 19 Jul 2007 03:49:14 +0000 http://www.halobrite.com/weblog/2007/07/18/5-reasons-why-iphone-application-development-doesnt-cut-the-digital-mustard/#comment-4 just a little nitpick - static positioning in CSS is the default positioning scheme, and is very different from fixed positioning. When an element is statically positioned, the browser determines it top and left based on the other elements in the "flow" before it. While the word typically means something akin to "fixed" in english, fixed positioning means something quite different in CSS. This is where an element is positioned with respect to to the bounding box of its first ancestor element that has a positioning context (is absolutely, relatively or fixed positioned), but, when the page scrolls, remains where it was initially positioned - unlike the near identical absolute positioning, where the element scrolls with the page. Sigh, I know that sounds complex, but a picture tells a thousand words on this one. So, static positioning is supported, but fixed is not ;-) john just a little nitpick - static positioning in CSS is the default positioning scheme, and is very different from fixed positioning.

When an element is statically positioned, the browser determines it top and left based on the other elements in the “flow” before it.

While the word typically means something akin to “fixed” in english, fixed positioning means something quite different in CSS. This is where an element is positioned with respect to to the bounding box of its first ancestor element that has a positioning context (is absolutely, relatively or fixed positioned), but, when the page scrolls, remains where it was initially positioned - unlike the near identical absolute positioning, where the element scrolls with the page.

Sigh, I know that sounds complex, but a picture tells a thousand words on this one.

So, static positioning is supported, but fixed is not ;-)

john

]]>