11–20 of 81 posts
JavaScript required to view the blog postings is a slight turn-off. What is the reasoning for it?
{"meta":{"status":200,"msg":"OK"},"response":{"blog":{"title":"rigoneri's blog","posts":11,"name":"rigoneri","url":"http:\/\/blog.rigoneri.com\/","updated":1339467147,"description":"","ask":false,"likes":0},"posts":[ ... ]} How does Google take to this? As far as I can tell it has to evaluate the JS before it can crawl the site; I got a few seconds of "Loading..." after the page had finished loading while it was pull…
https://www.google.com/search?q=google+bot+is+chrome edit: when I click on an external link and then click the back button, I get the JSON too even with chrome. This is bad.
The best way to circumvent the issue is to prevent the browser from caching the request (ex. cache busting via random querystring parameters), or to use different URLs for the HTML and JSON response (ex. appending '.json' to the end of the path).
Spotted a bug on this. If you go back or forward in your browser to a blog post, it just shows a bunch of JSON code. You have to reload to get the site to properly show.
Spotted a bug on this. If you go back or forward in your browser to a blog post, it just shows a bunch of JSON code. You have to reload to get the site to properly show.
$.ajaxSetup({ cache: false });
Spotted a bug on this. If you go back or forward in your browser to a blog post, it just shows a bunch of JSON code. You have to reload to get the site to properly show.
One minor complaint is with the scrollable slide-outs. When you scroll down through a slide-out like the Instagram one, and reach the bottom, the page behind starts scrolling.
This is a common problem, and why I dislike using scrollable areas on web pages in the first place. There must be a good way to fix this. I just don't want the outside area to scroll when my context is inside the small scrollable area.
The author's web site ( http://rigoneri.com/ ) is cited as an example "Syte", but when I view that page on my iPad the right-hand side of the page is chopped off. Doesn't seem to be all that responsive (despite the author's claims).
Spotted a bug on this. If you go back or forward in your browser to a blog post, it just shows a bunch of JSON code. You have to reload to get the site to properly show.