3 ms·

The conditions of the problem would be clearer if they didn't hide the extra form elements. But then they wouldn't be able to get the punch of "a simple form br

The conditions of the problem would be clearer if they didn't hide the extra form elements. But then they wouldn't be able to get the punch of "a simple form breaks iOS 7!"

deleted 13y ago
[deleted]
- heyitsnick 13y ago
  I'd love to know what the use-case is for a page with 6000 form items!
  - deleted 13y ago
    [deleted]
    - hk__2 13y ago
      Do you have a real-world example of a form with 500 inputs?
      - oakwhiz 13y ago
        Might I suggest a tax form?
        Samuel_Michon 13y ago
        Surely, those are divided in several steps/pages? Anything over 5 fieldsets and I’m sending it to the server first and then present a new page with the rest of the questions.
  - Pxtl 13y ago
    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.
    - Samuel_Michon 13y ago
      > 6000 fields is a 20x80 grid 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 13y ago
        ... oops. Dunno where my head was there.
- dpcx 13y ago
  Should I ask what form your company needs that actually has 5076 input fields?

The conditions of the problem would be clearer if they didn't hide the extra form elements. But then they wouldn't be able to get the punch of "a simple form breaks iOS 7!"

deleted 13y ago

[deleted]

heyitsnick 13y ago
I'd love to know what the use-case is for a page with 6000 form items!
- deleted 13y ago
  [deleted]
  - hk__2 13y ago
    Do you have a real-world example of a form with 500 inputs?
    - oakwhiz 13y ago
      Might I suggest a tax form?
      - Samuel_Michon 13y ago
        Surely, those are divided in several steps/pages? Anything over 5 fieldsets and I’m sending it to the server first and then present a new page with the rest of the questions.
- Pxtl 13y ago
  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.
  - Samuel_Michon 13y ago
    > 6000 fields is a 20x80 grid 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 13y ago
      ... oops. Dunno where my head was there.
dpcx 13y ago
Should I ask what form your company needs that actually has 5076 input fields?