Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What are the theoretical problems with hugely wide elements, like the image container of a carousel element. Are there any reasons why there would be a difference between a fixed container width of 10,000px or 1,000,000px ? At what point does performance become a realistic issue?
I am aware there are better ways to do this in practice (like calculating the width dynamically). I’m just interested in the maximums and problems related to huge elements.
You can’t have an exact number, it depends on OS memory management, browser memory management, physical memory, occupied memory (number of tabs and other running apps) and so on.
To be sure you don’t grind the browser (or OS) to a halt, and if you really must have a container that large, make sure to use some kind of lazy load for the content. An empty div is not a problem.
See this question for some numbers Determine Maximum Possible DIV Height