Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Untitled topic

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 53 posts

Re: undefined

#31

Post by Pxtl »

heyitsnick wrote: post #24
[deleted] wrote: post #14

Earlier quoted context omitted.

[deleted]

I'd love to know what the use-case is for a page with 6000 form items!

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.

Re: undefined

#32

Post by Samuel_Michon »

[deleted] wrote: post #25
Pxtl wrote: post #16

Earlier quoted context omitted.

Yeah. I get that it's a problem that iOS7 safari crashes with a lot of inputs, but that's an insanely-huge number of inputs. This is kind of an edge-case and you should probably avoid doing that in your web-pages. A hundred-ish inputs per-page is probably a better idea.

[deleted]

Parent suggested an example with hundred inputs. You made one with several hundred inputs, and even that one didn’t crash Safari.

It would’ve been better to simply concede that it’s an edge case. Putting thousands of inputs on a form is bad web development.

Re: undefined

#33

Post by Samuel_Michon »

Pxtl wrote: post #31
heyitsnick wrote: post #24

Earlier quoted context omitted.

I'd love to know what the use-case is for a page with 6000 form items!

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…

> 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.

Re: undefined

#34

Post by hk__2 »

[deleted] wrote: post #29
heyitsnick wrote: post #24

Earlier quoted context omitted.

I'd love to know what the use-case is for a page with 6000 form items!

[deleted]

Do you have a real-world example of a form with 500 inputs?

Re: undefined

#35

Post by [deleted] »

Samuel_Michon wrote: post #32
[deleted] wrote: post #25

Earlier quoted context omitted.

[deleted]

Parent suggested an example with hundred inputs. You made one with several hundred inputs, and even that one didn’t crash Safari. It would’ve been better to simply concede that it’s an edge case. Putting thousands of inputs on a form is bad web development.

[deleted]

Re: undefined

#37

Post by racl101 »

film42 wrote: post #15

To be fair though, that form has like 5-6 thousand hidden inputs.

Yah, if you've got that many fields in your form you're doing it wrong and you need psychiatric help.

Re: undefined

#38

Post by Samuel_Michon »

[deleted] wrote: post #35
Samuel_Michon wrote: post #32

Earlier quoted context omitted.

Parent suggested an example with hundred inputs. You made one with several hundred inputs, and even that one didn’t crash Safari. It would’ve been better to simply concede that it’s an edge case. Putting thousands of inputs on a form is bad web development.

[deleted]

Right, Apple never fixes bugs and HN doesn’t understand demonstrations. People continue to disappoint, don’t they.

You found a bug. Kudos, but one of the reasons we haven’t heard about it before is because most people won’t encounter forms with thousands of inputs. It would’ve been helpful if you had filed a Radar, then the only party who can actually fix it would know about it. You chose not to. Instead, you made a misleading post to HN. And as you may well have noticed, HN readers don’t like to be tricked.

Post reply on HN