11–20 of 58 posts
I wish his "HTML 5 from early 2008" site would support zooming on my iPad, pretty obnoxious it doesn't.
I wish his "HTML 5 from early 2008" site would support zooming on my iPad, pretty obnoxious it doesn't.
I wish people stopped complaining on HN that linked websites don't work on their iPads, and instead sent bug reports to Apple or authors of the websites.
I think the best way to do it would be an XML file referenced from a meta tag. This is a property of websites, not web pages, so it makes sense to put all the information in one place. Ars Technica http://arstechnica.com/ Ars Technica: Serving the technologist for 1.2 decades News http://arstechnica.com/ http://arstechnica.com/favicon.ico Features http://arstechnica.com/features/ http://static.arstechnica.net/ie-jump…
[1] http://www.whatwg.org/specs/web-apps/current-work/multipage/...
Just FYI, you've got a typo in your markup that's preventing your page from validating: should be
Actually it's not me the author. I run in the link at reddit (the conversation there wasn't that interesting about the topic) so i thought to submit it here. Take care, _e_ Ps: I sent an email to the author of the blog post inviting him to join the conversation here. If interested.
Earlier quoted context omitted.
I wish people stopped complaining on HN that linked websites don't work on their iPads, and instead sent bug reports to Apple or authors of the websites.
Well, for that matter HN has a fixed minimum width defined which makes it unable to display properly on an iPad (ie. without scrolling back and forth to read comments).
I think the best way to do it would be an XML file referenced from a meta tag. This is a property of websites, not web pages, so it makes sense to put all the information in one place. Ars Technica http://arstechnica.com/ Ars Technica: Serving the technologist for 1.2 decades News http://arstechnica.com/ http://arstechnica.com/favicon.ico Features http://arstechnica.com/features/ http://static.arstechnica.net/ie-jump…
Yeah, a reference to an external file would be a better way to do it. And HTML5 already has the mechanism for this sort of thing: the element[1] and the "rel extensions" registry. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/... [2] http://wiki.whatwg.org/wiki/RelExtensions
Earlier quoted context omitted.
Yeah, a reference to an external file would be a better way to do it. And HTML5 already has the mechanism for this sort of thing: the element[1] and the "rel extensions" registry. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/... [2] http://wiki.whatwg.org/wiki/RelExtensions
Uh, doesn't that just add an extra round trip and yet another mandatory HTTP request? No thanks, I think we've enough of those.
No. The request only happens if you decide to "pin" the site, or otherwise give it a first-class status on your machine (one could imagine the same by pining it to the OSX dock or making a site into a "standalone app", I think there was a browser doing that a while ago)