The much-touted "Reader" function is apparently broken in my Safari 5. I've visited dozens of websites and have yet to see a "Reader" icon appear in the address bar. Also, trying to invoke Reader manually (Command-Shift-R or choosing View->Enter Reader) does nothing; the menu item is always greyed out. The browser seems otherwise fully functional, so I'm curious if anyone else is finding the feature non-working in their Safari 5.
Bee & Chromey: Yes, both those pages DO bring up the Reader icon. Wow--I guess I had been extraordinarily unlucky in that all the other pages I visited were not compatible with the feature. Unfortunately, those are the pages I most frequent, so I guess the feature will not be of much use to me. But in any case, thanks for directing me to Reader-compatible pages.
I guess that begs the question though: What makes a page Reader-compatible or Reader-incompatible? It sure doesn't work on NYT, AppleInsider, my local paper (delawareonline.com), Engadget, etc.
Adding to Bee's helpful post, seems only those web sites meeting specific content criteria show the Reader option in the Address Bar. BTW, this new feature works really well. Very clean and easy to use. to try (MacWorld article for iPhone 4).
Let us know if "Reader" shows up when accessing the suggested sites.
Just saw your post. Have to be fast around here, it seems. 😉
Reader does appear for Apple Insider articles.
Try this one - note, Reader does not appear on article summary pages, only on the page where the entire article appears.
I have wordpress-based articles that Reader cannot read... After some tests, it seems that in order for Reader to work, the articles must be longer than the height of the browser.
Would love to know specifically what the criteria are for triggering the Reader Function. I'm guessing since we
are guessing, there's no exact info from Apple?
The text being longer than the page is highly likely, but what else? Perhaps an HTML 5 tag like <article> ?
@Hawaiian_Starman, that's great, thanks. Already some serious testing being conducted, I see. Would be nice if Apple would actually publish the details themselves, but this is very helpful.
Looking at arc90's code in their .js file, I see this comment:
"Using a variety of metrics (content score, classname, element types), find the content that is
* most likely to be the stuff a user wants to read. Then return it wrapped up in a div"