Well, my problem is that I am attaching CVE's to IAVAs. There is over 15,000 CVEs. In order for ME (the only one using this page) to add the CVE's, I need to be able to display them all. Each IAVA can have multiple CVE's. Sometimes they are all over the place.
What the users will see is any information pertaining to an IAVA when they do a search. Thats all the users can do is search this database and return results. They do not enter any information into it.
The problem is not with HTML and it is not with the browser
The problem is your computer.
This does not mean that there is anything wrong with your computer, it is just running out of memory when trying to cope with 15,000 items.
You will just have to think of another way of doing this.
May be split the list between two
This sounds like a job for a database connected to an Autocomplete widget. I won't go into too much detail here; you've seen these all over the web. The best example I can think of is Yahoo!'s very own UI Library component, written by the inimitable Jenny Han and linked below. I've also included a link to the Yahoo! Design Patterns library, which has an excellent storyboard for Autocomplete.
2006-08-15 17:07:09
·
answer #2
·
answered by Kent Brewster3
·
0⤊0⤋
These acronyms you are using are confusing, but you may want to try to add a categorization scheme for these 'CVE's and 'IAVA's. Because you used acronyms, I don't know if that is possible, but if you are running into a limit, whether inimical to they standard or just set up by your browser, this is the best way around it.
2006-08-15 16:49:19
·
answer #3
·
answered by John J6
·
0⤊1⤋
I think there is not limit, but nevertheless, to display more than 1000 items is a little tired to read. May be if you make groups of items by categories would be faster and easier to display and read.
since you said after 1000 items it doesn't display something, then I guess there should be a limit. make sure you didn't close any tags. as far as I know, there are no limits in html. anyway, what do you need it for?
The official W3C specs don't mention a limit, however, the browsers themselves may artificially create one. Have you tried a browser other than the one you are currently using?