5 ms·

Side note: The scrolling on this page is horribly broken on Android. I can't even read the whole article because I can't scroll down. After loading the article

Side note: The scrolling on this page is horribly broken on Android. I can't even read the whole article because I can't scroll down. After loading the article on m laptop I must say that it is a fascinating article and will change how I think of documentation. For example, soon my company will be making a change that will render the old wiki url's incorrect, the problem is that many older documents will still refer to the old url's. I think we should have some sort of list of the old wiki url's (there is an even older set of url's as well) to help future archeologists in piecing together the information.

Mz 15y ago
Side note: The scrolling on this page is horribly broken on Android. I can't even read the whole article because I can't scroll down. I'm on a netbook and it was pretty bad. But, yes, excellent and thought provoking article.
karamazov 15y ago
Out of curiosity, why don't you have the old url just point to the new one?
rubyrescue 15y ago
hi - any ideas how to fix it? wrttn.in is my site and i can make a change to the css or rendering if necessary...
- swang 15y ago
  It scrolls very slowly on my orig iPad. Also iOS scroll to top feature seems broken
- evmar 15y ago
  (I am a Chrome developer.) I glanced at your scroll.css and saw a bunch of rules that attempt to fiddle with the overflow/position attributes. This sort of thing confuses all browsers. Why not just use a normal scrollbar? It's fine to change the way it looks it if you want using the -webkit-scrollbar stuff you've done, but hacking out the normal web page scroll bar confuses everything. There are, for example, optimization opportunities in web rendering engines that only hit when the page is "normal" (which probably explains the poor performance other people are encountering). (I noticed even on desktop Chrome the scrolling isn't smooth, unlike other pages. Probably for the same reason.)
  - rubyrescue 15y ago
    thanks, this is incredibly helpful, and one of the reasons i hang out here. i'll remove some of that and post up a version later today...
leif 15y ago
where you see wrttn.in/XXXXXX, change it to wrttn.in/api/XXXXXX, that seems to fix scrolling

Mz 15y ago

Side note: The scrolling on this page is horribly broken on Android. I can't even read the whole article because I can't scroll down. I'm on a netbook and it was pretty bad. But, yes, excellent and thought provoking article.

karamazov 15y ago

Out of curiosity, why don't you have the old url just point to the new one?

rubyrescue 15y ago

hi - any ideas how to fix it? wrttn.in is my site and i can make a change to the css or rendering if necessary...

swang 15y ago
It scrolls very slowly on my orig iPad. Also iOS scroll to top feature seems broken
evmar 15y ago
(I am a Chrome developer.) I glanced at your scroll.css and saw a bunch of rules that attempt to fiddle with the overflow/position attributes. This sort of thing confuses all browsers. Why not just use a normal scrollbar? It's fine to change the way it looks it if you want using the -webkit-scrollbar stuff you've done, but hacking out the normal web page scroll bar confuses everything. There are, for example, optimization opportunities in web rendering engines that only hit when the page is "normal" (which probably explains the poor performance other people are encountering). (I noticed even on desktop Chrome the scrolling isn't smooth, unlike other pages. Probably for the same reason.)
- rubyrescue 15y ago
  thanks, this is incredibly helpful, and one of the reasons i hang out here. i'll remove some of that and post up a version later today...

leif 15y ago

where you see wrttn.in/XXXXXX, change it to wrttn.in/api/XXXXXX, that seems to fix scrolling