carrying over content to next div
I want to make a newspaper type website (scrolling content horizontally).
Any Ideas?
or how can I carry content between divs once the content fills the first div, the rest carries over the the next?
Any Ideas?
or how can I carry content between divs once the content fills the first div, the rest carries over the the next?
Dave Baldwin
HTML <div>s don't do that. No HTML element will flow text from one to the next. Even if you find a way to program it... different size screens will cause the <div> to be different sizes unless you have done something to restrict it. And there is nothing that I know of that will tell you "when a div is full".
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
A plugin that comes in a 148k zip; indicating an even bigger size in use. So a big bloated approach instead of learning how to write about a hundred bytes of actual CSS code?
I guess that makes sense if you are trying to avoid learning how to code. If that much bloat was necessary then you do what you have to do but logically that plugin makes as much sense as using a railway car to transport a bag of pretzels.
The plugin needs 100k+ to generate the CSS in the DOM either in the stylesheet object or in some non-standard object of its own. So more than 99.9% of the plugin is overhead to do the same thing as 100 bytes. Efficient; very efficient. No sense having a lot of memory and bandwidth if you can't find ways to waste it.
Cd&
I guess that makes sense if you are trying to avoid learning how to code. If that much bloat was necessary then you do what you have to do but logically that plugin makes as much sense as using a railway car to transport a bag of pretzels.
The plugin needs 100k+ to generate the CSS in the DOM either in the stylesheet object or in some non-standard object of its own. So more than 99.9% of the plugin is overhead to do the same thing as 100 bytes. Efficient; very efficient. No sense having a lot of memory and bandwidth if you can't find ways to waste it.
Cd&
I've requested that this question be closed as follows:
Accepted answer: 250 points for hankknight's comment #a39799923
Assisted answer: 250 points for COBOLdinosaur's comment #a39795501
for the following reason:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Accepted answer: 250 points for hankknight's comment #a39799923
Assisted answer: 250 points for COBOLdinosaur's comment #a39795501
for the following reason:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
ASKER
Thank you to you all.
Thanks COBO, you make alot of sense.
Thanks COBO, you make alot of sense.
ASKER
Get point COBO!
ASKER
Thanks all!