Overarching experience discussion about regulations-site HOT 4 CLOSED

My biggest question/concern with infinite scroll, is what happens when a user skips to the bottom of the regulation through the navigation? Do all of the preceding sections load, or does the scroll work both ways? I also think we may run in to performance issues when a huge chunk of text is loaded, regardless of it having been done so dynamically or not.

That said, I really like the idea of being able to view the entire reg in one documents.

In terms of non-js users, is it safe to presume less-capable devices or slower connections? If so, I would say we need to create a paged experience, but I am admittedly unsure of the research on this.

from regulations-site.

I think we'd expect the scroll to work both ways. Performance issues could crop up, although we could potentially manage memory by discarding things we haven't needed in a while. I'm also not sure how much of an issue performance is going to be for most devices.

Regarding no-js, at the moment I'm thinking about the fuss e FSF is kicking up about regs.gov. But yes, it would also support older devices/browsers instead of trying to backfill the js support.

from regulations-site.

One issue I foresee with the infinite scroll is that we may load more content than the user wants to see. If a user gets to the bottom of the section they are looking at and the next section loads without their consent. Would that cause performance issues or make it easier for the user to get lost in the content?

from regulations-site.

I think I have a solution to this that will keep a smooth user experience and make it function more like a single document but without the performance issues we're all concerned about. Definitely something for my to-do list this sprint.

from regulations-site.