I could easily see it coming up in survey-software or massive legal forms where paging is implemented via hide/show. This is a bit of an abuse of the hide/show mechanic, but I've written abominations like that myself.
Yes, books of paper forms with over 6000 fields can happen. Especially common if you've got a lot of "only fill the one out of these 10 forms that are relevant to you" kind of layout, or cases where you're using forms in a tabular layout - 6000 fields is a 20x300 (dunno why I said 80 a moment ago) grid. Large, but not unthinkable. 300 lines of a personnel directory with 20 fields on each?
Imagine you've got a scrollable list of something and have 20 visible textbox elements in each list entry?
This kind of stuff was super-common back before AJAX. I could see supporting an internal application and having this problem, for example.
Huh, how does that work? According to my math, it would be a 20x300 grid, and every single field would have to have an input element on it. That’s pretty darn big.
Pxtl|12 years ago
Yes, books of paper forms with over 6000 fields can happen. Especially common if you've got a lot of "only fill the one out of these 10 forms that are relevant to you" kind of layout, or cases where you're using forms in a tabular layout - 6000 fields is a 20x300 (dunno why I said 80 a moment ago) grid. Large, but not unthinkable. 300 lines of a personnel directory with 20 fields on each?
Imagine you've got a scrollable list of something and have 20 visible textbox elements in each list entry?
This kind of stuff was super-common back before AJAX. I could see supporting an internal application and having this problem, for example.
Samuel_Michon|12 years ago
Huh, how does that work? According to my math, it would be a 20x300 grid, and every single field would have to have an input element on it. That’s pretty darn big.
unknown|12 years ago
[deleted]
hk__2|12 years ago