how to privent page break when printing long HTML page?

I have a long report in HTML code and I print it
whith mtrix printer.
is it possible to privent page breaks when printing HTML page?


thanks?

prevent and then what? what will happen to the rest of the document which can't fit in the first printed page?

There are some advanced CSS2 and CSS3 properties and selectors (with psuedo-classes) that define page-breaks and etc...

However, IE6 doesn't support them (Surprise, surprise) and AFAIK, the "IE7" patch doesn't fix them either

Its really just a matter of luck really.... there's nothing else to do untill M$ fixes their broken browsers (well, they're not the only guilty parties... Firefox doesn't support CSS3 Printing either (shock horror!))

broken or not broken, it's the most popular browser for now, because it's extremely comfortable to use... over time other browsers will become comfortable as well and ppl will open their eyes.
well dude (btw, 1337 means "leet" by any chance??) why won't you develop new browser which will support all kinds of cool features?

*rises to the challenge*

My 'nick on this forum is a parody of the 13 yearold "wannabees" who talk in a hybrid of "txt" and "1337-sp33k", because the other forum sites I regular on, such as Deezire, and TutorialForums are so chock-full of them.... I was expecting the same here actually

And as regards making my own browser....

It would be pointless... writing a HTML Rendering engine can take *years*, and even for a small team, both the Gecko and KHTML Engines are the best around

Besides, they can't support CSS3 untill its standardised.... this is why Navigator 4 was so poor in the area of standards compliance, because Netscape wrote the browser to work with JSSS, which is technically superior to CSS, but the JSSS proposal was turned down in favour of the simpler CSS, by the time the news came through, Netscape didn't have the time to add CSS support, and the result was a broken browser

And yes, I do have to agree that Internet Explorer is a "good" browser, what with UI consistency in a familiar environment, and at the time it was standards compliant.... this was, however, more than 3 years ago.... web-standards have changed since then, and the XHTML2.0 Proposal is likely to become standard within 6 months from now, Longhorn (and thus, the next edition of IE) isn't due out for another 2 years

Basically, Microsoft needs to fix IE for modern standards and add tabbed-browsing otherwise the fate of the internet as we know it is uncertain.... (please... I don't want any more 12 yearold script-kiddies using FrontPage and *shudders* <frameset> to break the internet)

But I can see why Microsoft isn't keen on adding tabbed-browsing.... because Microsoft is pushing for an SDI UI throughought.... thing is, practically everyone prefers MDI to SDI, the "tabbed" experience in VisualStudio 2003 is testement to the fact that Microsoft *can* make a good "tabbed" program, it would not be too hard to add it to Explorer

Still, we do, technically, have Netscape Communications (the company) to thank for breaking IE in the first place.... it was their "internet = next application" paradgym (sp?) that caused Microsoft to integrate IE with the core OS UI, after perceiving Netscape's statement as a threat to their market superiority (and hence... monopoly) with the end result being a stagnant browser using 8 yearold code

-1337_d00d

all that said, what's your opinion on GBrowser, or whatever name it would finally have? you expect it would be better than all the current browsers? After all, rumor say they hired one of the top developers of the original IE browser...

Being the cynic I am, I suspect Google will use GBrowser as a marketing tool and have google ads in the browser chrome, much like the free version of Opera does, probably with a subscription or one-off payment to get rid of them, with the typical "text ads based on the content in your browser window"

(laugh all you want, but its probably true)

they'll probably do an Opera clone, licensing the KHTML Engine *probably*, I can't see them using Gecko, or they *could* theoretically buy-out Opera... I can see that happening, what with the recent windfall after floating on the stock-market

That besides.... I don't think they'd be specifically aiming for standards compliance... I mean, run Google.com itself through the W3C CSS and HTML validators, if their browser does support standards, its likely to just be a by-product of licensing a good engine

If anything, they're going to outsource or buy-in developers, all their current software engineers and staff are all in the field of searching

...for shame they haven't yet searched for a good site source code

well, nothing is perfect and can't be perfect. question here is, whether that new browser will be better than the current browsers or not... probably it won't be, in my opinion - just another gimmick by Google Wizards. Time Will Tell...