51–58 of 58 posts
Speaking of stopping the madness, this guy's website uses a fixed viewport that prevents iPad Safari from zooming in and out. Stop the madness, indeed.
If you read what you saw and it made absolutely no sense, there is actually more below the image. The footer makes it look like the article has ended. It's like a frame but with no apparent scrollbar. Terrible non-intuitive webdesign (sure looks fancy though). Here is how it looks like for me: http://s1.image.gd/o/d6/d63da036dc4e2e93670dac425ca017d9b227...
Just FYI, you've got a typo in your markup that's preventing your page from validating: should be
Earlier quoted context omitted.
Because it's ironic that he's being a stickler for standards when his own site is broken.
There is nothing ironic in the fact that people cannot afford to test their websites on every single device Apple releases. FYI, I just opened that website on my iPhone and it works great. Perhaps, the viewport meta tag was added here with iPhone in mind, before iPad was released. Edit: indeed, this is a bug: there are different CSS styles for devices with 480px (via @media CSS rules). Desktop browsers pick the latte…
Earlier quoted context omitted.
> I don't buy the idea of hijacking a menu tag to alter browser chrome. The tag does it with no big issue. Though an external ed file (à la RSS/ATOM) would be much better. Meta tags are not really structured and forces everybody to download a bunch of browser-specific crap they don't carte for. > As an aside, I can tell you that if they'd implemented it as a menu tag, we wouldn't have put it on Ars for the purposes o…
Because as people have already said, doing a CSS hack so that your hack doesn't display in the page itself is worse than doing the standards-compliant method of implementing the browser-specific feature via the meta tag. Here[1] you can see that the standard places no restrictions on what can be entered in the name option and the browser is not required to implement handlers for all names. Given that this is not disp…
A jump list isn't an HTML document - I'm not sure describing it with html tags makes sense, since it'd be too easy to write invalid jumplist markup that's valid HTML. I could envisage somehow replacing RSS with HTML (use the right tags, in the right order, don't use the wrong tags), but it wouldn't make much sense.
> A jump list isn't an HTML document A jump list isn't a bunch of metas either. An HTML or a specific, custom XML format can be ways to describe jumplists. These descriptions are then translated into whatever actual format jumlist specs use. No problem. > I'm not sure describing it with html tags makes sense A jump list is a menu. So is a element. You could hardly make more sense.
Earlier quoted context omitted.
Because as people have already said, doing a CSS hack so that your hack doesn't display in the page itself is worse than doing the standards-compliant method of implementing the browser-specific feature via the meta tag. Here[1] you can see that the standard places no restrictions on what can be entered in the name option and the browser is not required to implement handlers for all names. Given that this is not disp…
I don’t think you understand what “CSS hack” means.
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…