Fucking URL bars in iOS are now causing me pain. What the fuck is up with these things?
-
-
Replying to @rossbruniges
@rossbruniges for extra credit, bringing up the keyboard doesn't change the document size so position:bottom stuff stays under the kb.2 replies 0 retweets 0 likes -
Replying to @sil
@sil Maybe because documents shouldn’t be pinning fake chrome to an app (the browser)? Have seen many abuses of this on sites+@rossbruniges1 reply 0 retweets 0 likes -
Replying to @aral
@aral@rossbruniges you're suggesting that anything at all with position:absolute, bottom: something is "fake chrome"?2 replies 0 retweets 0 likes -
Replying to @sil
@sil@rossbruniges Nope; just that I’ve seen it abused for that—maybe that’s why it’s been dropped. Would like to know reasoning behind it.1 reply 0 retweets 0 likes -
Replying to @aral
@aral@rossbruniges me too. I see no reason why I shouldn't be allowed to deliver something that looks like an app, on the web. :(2 replies 0 retweets 0 likes -
Replying to @sil
@sil One reason is because it’s an app-within-an-app. Case in point, my bugbear: 2 nav bars, 2 toolbars+@rossbrunigespic.twitter.com/lhTERxKOzl
1 reply 0 retweets 0 likes -
Replying to @aral
@aral@rossbruniges so your argument is honestly that delivering an app experience on the web is a flat-out no-no? (Not accusation; clarity)6 replies 0 retweets 0 likes
@sil For the sake of usability, I would prefer that an app running in an app adopted its own culture & didn’t try to… +@rossbruniges
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.