... the creators of LOST really decided to get rid of some characters—probably so they wouldn't have to develop their stories, for there is already way too many—and drastically change some of the surviving ones? C'mon, Ben is now growing surprisingly 007-ish, and the way he handled those two poor AK-armed nomads in a desert was very much Jason-Bourne-like; move over, XXX, we have a new action hero in town (in all fairness, though, the real spies and assassins probably all look like Ben, and not like James Bond)... nevertheless, fun to watch. I never believed that they will get out of the LOST storytelling maze gracefully, and so far I see no indications of the plot coming together. Oh, well.
I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic