PrintWindow()

**Lasse Reichstein Nielsen** · Jul 20 '05, 09:17 AM

Re: PrintWindow()

"OysterCrac ker" <oc@sc.rr.com > writes:
[color=blue]
> Hi - I've used the <a href="javascrip t:printWindow() "><Print></a>[/color]

Don't use the javascript: pseudo protocol.
<URL:http://jibbering.com/faq/#FAQ4_24>

I don't know the printWindow function, but I guess it calls window.print.
I assume you don't write "<Print>" in HTML :)
[color=blue]
> function for printing a webpage, but I ran into an interesting variation
> recently, and would appreciate some help duplicating it. Unfortunately, the
> webpage had locked out both the right-mouse menu and the status bar, so I
> couldn't sneak a peek.[/color]

Give me the link, and I'll have the code for you in ten seconds (I use
Opera which don't allow the web page to remove either). Alternatively,
you could just have turned Javascript off while studying the page.
[color=blue]
> The "Print" link was located on a full-color, web-friendly page, but when a
> viewer clicked the link, a b&w, printer-friendly version opened in a very
> small window, then proceeded as usual with the "javascript:pri ntWindow()"
> function.[/color]

Why not just use a different stylesheet with media=print?

Still, it's nothing fancy. They just open the page with a call to
window.open. The loaded page itself calls its window.print function
when it is finished loading (e.g. <body onload="window. print()">).

Btw, I searched for "printWindo w" and found the same lousy script a
few times (including the href="javascrip t:" method of calling it and
often also a bunch of HTML comments inside the script tag):
---
<SCRIPT LANGUAGE="JavaS cript">

</script>
---
This is horrible in so many different ways that I don't know where to
begin. The following will do the same, only safer and working in any
new browsers with appVersion<4:
---
<script type="text/javascript">
function printWindow(){
if (window.print) {
window.print();
}
}
</script>
---

/L
--
Lasse Reichstein Nielsen - lrn@hotpop.com
Art D'HTML: <URL:http://www.infimum.dk/HTML/randomArtSplit. html>
'Faith without judgement merely degrades the spirit divine.'

**Zac Hester** · Jul 20 '05, 09:17 AM

Re: PrintWindow()

"OysterCrac ker" <oc@sc.rr.com > wrote in message
news:h1iTa.3359 16$jp.8809499@t wister.southeas t.rr.com...[color=blue]
> Hi - I've used the <a href="javascrip t:printWindow() "><Print></a>
> function for printing a webpage, but I ran into an interesting variation
> recently, and would appreciate some help duplicating it. Unfortunately,[/color]
the[color=blue]
> webpage had locked out both the right-mouse menu and the status bar, so I
> couldn't sneak a peek.
>
> The "Print" link was located on a full-color, web-friendly page, but when[/color]
a[color=blue]
> viewer clicked the link, a b&w, printer-friendly version opened in a very
> small window, then proceeded as usual with the "javascript:pri ntWindow()"
> function.
>
> How do I do that? Thanks,
> ~OC~[/color]

The only way to know is to look at the source.

By the way, there's no reason you can't look at the source code. If they
disable right-clicking and that really is the only way your browser allows
you to view source, do this:

1. Right-click on the page or frame and *hold* the mouse button down.
2. When the pop-up dialog opens telling you you can't right-click, press the
"Enter" key on your keyboard.
3. Now, release the mouse button and you will have your right click menu
just like nothing ever happened.

You could also disable JavaScript, or use the pull-down menu to view source.

To answer your question, the easiest solution (assuming the site is
databased on the backend) to providing printable versions of web content is
to handle everything server-side. JavaScript and CSS can do this, but it's
very unreliable and is difficult to get working on everyone's browser. I've
developed many commercial web sites who wanted a printable version of all of
their content, and it was very simple to just implement multiple rendering
formats through my server's execution environment (in my case PHP).

HTH,
Zac

**Mosley Jones III** · Jul 20 '05, 09:17 AM

Re: PrintWindow()

"Zac Hester" <news@planetzac .net> wrote in message
news:3f1dd2bc$1 @news.enetis.ne t...[color=blue]
> "OysterCrac ker" <oc@sc.rr.com > wrote in message
> news:h1iTa.3359 16$jp.8809499@t wister.southeas t.rr.com...[color=green]
> > Hi - I've used the <a href="javascrip t:printWindow() "><Print></a>
> > function for printing a webpage, but I ran into an interesting variation
> > recently, and would appreciate some help duplicating it. Unfortunately,[/color]
> the[color=green]
> > webpage had locked out both the right-mouse menu and the status bar, so[/color][/color]
I[color=blue][color=green]
> > couldn't sneak a peek.
> >
> > The "Print" link was located on a full-color, web-friendly page, but[/color][/color]
when[color=blue]
> a[color=green]
> > viewer clicked the link, a b&w, printer-friendly version opened in a[/color][/color]
very[color=blue][color=green]
> > small window, then proceeded as usual with the[/color][/color]
"javascript:pri ntWindow()"[color=blue][color=green]
> > function.
> >
> > How do I do that? Thanks,
> > ~OC~[/color]
>
>
> The only way to know is to look at the source.
>
> By the way, there's no reason you can't look at the source code. If they
> disable right-clicking and that really is the only way your browser allows
> you to view source, do this:
>
> 1. Right-click on the page or frame and *hold* the mouse button down.
> 2. When the pop-up dialog opens telling you you can't right-click, press[/color]
the[color=blue]
> "Enter" key on your keyboard.[/color]

nonsense

if the context event has been told not to fire it wont, what Zac meant was
he cannot stop you geting the menu others can. stopping a event firing is
very basic.
here is a example, you will see that no such thing is possible on my page. I
have also set up a interface where you can enter your URL you need to see
and it will present the code for you

[color=blue]
> 3. Now, release the mouse button and you will have your right click menu
> just like nothing ever happened.
>
> You could also disable JavaScript, or use the pull-down menu to view[/color]
source.[color=blue]
>
> To answer your question, the easiest solution (assuming the site is
> databased on the backend) to providing printable versions of web content[/color]
is[color=blue]
> to handle everything server-side. JavaScript and CSS can do this, but[/color]
it's[color=blue]
> very unreliable and is difficult to get working on everyone's browser.[/color]
I've[color=blue]
> developed many commercial web sites who wanted a printable version of all[/color]
of[color=blue]
> their content, and it was very simple to just implement multiple rendering
> formats through my server's execution environment (in my case PHP).
>
> HTH,
> Zac
>
>[/color]

**Lasse Reichstein Nielsen** · Jul 20 '05, 09:18 AM

Re: PrintWindow()

"Zac Hester" <news@planetzac .net> writes:
[color=blue]
> What are you labeling as "nonsense?" My method of subverting "right-click
> trapping" or his inability to view the source of a given web page?[/color]

Your method, if I read him right.
Just write
<body oncontextmenu=" return false">
in a page and try your method. No pop-up dialog at all, works in both
IE and Mozilla (and should be a hanging offense in real pages, ofcourse).

He is, however, a little too confident in that method, since turning
off javascript will stop it cold. Who cares, though, there is no
functionality in the normal context menu that isn't available through
the menu anyway.

....[color=blue]
> Post a URL to your page that claims to be able to hide the source code from
> a visitor, and I'll have a look. If I can't get to your code, this round is
> on me.[/color]

Pretty much a safe bet.

Not even encryption, as long as it is decrypted clientside, will stop
a determined attacker.

/L
--
Lasse Reichstein Nielsen - lrn@hotpop.com
Art D'HTML: <URL:http://www.infimum.dk/HTML/randomArtSplit. html>
'Faith without judgement merely degrades the spirit divine.'

**Zac Hester** · Jul 20 '05, 09:18 AM

Re: PrintWindow()

"Lasse Reichstein Nielsen" <lrn@hotpop.com > wrote in message
news:smoxf5uy.f sf@hotpop.com.. .[color=blue]
> "Zac Hester" <news@planetzac .net> writes:
>[color=green]
> > What are you labeling as "nonsense?" My method of subverting[/color][/color]
"right-click[color=blue][color=green]
> > trapping" or his inability to view the source of a given web page?[/color]
>
> Your method, if I read him right.
> Just write
> <body oncontextmenu=" return false">
> in a page and try your method. No pop-up dialog at all, works in both
> IE and Mozilla (and should be a hanging offense in real pages, ofcourse).
>
> He is, however, a little too confident in that method, since turning
> off javascript will stop it cold. Who cares, though, there is no
> functionality in the normal context menu that isn't available through
> the menu anyway.[/color]

I saw that method on some hacker-ese page once. I found it funny since they
had all kinds of JavaScript traps that I learned how to use by looking right
at their code. They even packaged up all their JavaScript in nice,
easy-to-download external script files. It's been a while, but I'm pretty
sure Konquerer (Gecko-based, I think) didn't fire the oncontextmenu event.
However, I seem to remember using a browser on Windows that didn't fire the
event either. (Maybe an old version of Netscape or something.)
Additionally, has anyone on a Mac OS had problems with context-sensitive
menus employing this trick?

The method I suggested was based on my experience of 99% of those pages that
try to lock out the context menu by simply popping up an alert box. The
casual visitor becomes disoriented by this and decides that there must not
be a way to use the context menu. The person trying to quickly view the
source of an internal frame, learns that this method is easier than digging
through the Internet cache.

Take care,
Zac

**Mosley Jones III** · Jul 20 '05, 09:18 AM

Re: PrintWindow()

"Zac Hester" <news@planetzac .net> wrote in message
news:3f1ede82$1 @news.enetis.ne t...[color=blue]
> "Lasse Reichstein Nielsen" <lrn@hotpop.com > wrote in message
> news:smoxf5uy.f sf@hotpop.com.. .[color=green]
> > "Zac Hester" <news@planetzac .net> writes:
> >[color=darkred]
> > > What are you labeling as "nonsense?" My method of subverting[/color][/color]
> "right-click[color=green][color=darkred]
> > > trapping" or his inability to view the source of a given web page?[/color]
> >
> > Your method, if I read him right.
> > Just write
> > <body oncontextmenu=" return false">
> > in a page and try your method. No pop-up dialog at all, works in both
> > IE and Mozilla (and should be a hanging offense in real pages,[/color][/color]
ofcourse).[color=blue][color=green]
> >
> > He is, however, a little too confident in that method, since turning
> > off javascript will stop it cold. Who cares, though, there is no
> > functionality in the normal context menu that isn't available through
> > the menu anyway.[/color]
>
> I saw that method on some hacker-ese page once. I found it funny since[/color]
they[color=blue]
> had all kinds of JavaScript traps that I learned how to use by looking[/color]
right[color=blue]
> at their code. They even packaged up all their JavaScript in nice,
> easy-to-download external script files. It's been a while, but I'm pretty
> sure Konquerer (Gecko-based, I think) didn't fire the oncontextmenu event.
> However, I seem to remember using a browser on Windows that didn't fire[/color]
the[color=blue]
> event either. (Maybe an old version of Netscape or something.)
> Additionally, has anyone on a Mac OS had problems with context-sensitive
> menus employing this trick?
>[/color]

yes only yesterday you were informing a user that all he has to do is hod
down the mouse button while he presses the enter button on the keyboard.

Yo made a error, but in your quest to hide this you have attracted attention
to yourself

[color=blue]
> The method I suggested was based on my experience of 99% of those pages[/color]
that[color=blue]
> try to lock out the context menu by simply popping up an alert box. The
> casual visitor becomes disoriented by this and decides that there must not
> be a way to use the context menu. The person trying to quickly view the
> source of an internal frame, learns that this method is easier than[/color]
digging[color=blue]
> through the Internet cache.
>
> Take care,
> Zac
>
>[/color]

**Zac Hester** · Jul 20 '05, 09:19 AM

Re: PrintWindow()

"Mosley Jones III" <me@info.gov.ma rs> wrote in message
news:3f1f4d69@f unnel.arach.net .au...[color=blue]
>
> "Zac Hester" <news@planetzac .net> wrote in message
> news:3f1ede82$1 @news.enetis.ne t...[color=green]
> > "Lasse Reichstein Nielsen" <lrn@hotpop.com > wrote in message
> > news:smoxf5uy.f sf@hotpop.com.. .[color=darkred]
> > > "Zac Hester" <news@planetzac .net> writes:
> > >
> > > > What are you labeling as "nonsense?" My method of subverting[/color]
> > "right-click[color=darkred]
> > > > trapping" or his inability to view the source of a given web page?
> > >
> > > Your method, if I read him right.
> > > Just write
> > > <body oncontextmenu=" return false">
> > > in a page and try your method. No pop-up dialog at all, works in both
> > > IE and Mozilla (and should be a hanging offense in real pages,[/color][/color]
> ofcourse).[color=green][color=darkred]
> > >
> > > He is, however, a little too confident in that method, since turning
> > > off javascript will stop it cold. Who cares, though, there is no
> > > functionality in the normal context menu that isn't available through
> > > the menu anyway.[/color]
> >
> > I saw that method on some hacker-ese page once. I found it funny since[/color]
> they[color=green]
> > had all kinds of JavaScript traps that I learned how to use by looking[/color]
> right[color=green]
> > at their code. They even packaged up all their JavaScript in nice,
> > easy-to-download external script files. It's been a while, but I'm[/color][/color]
pretty[color=blue][color=green]
> > sure Konquerer (Gecko-based, I think) didn't fire the oncontextmenu[/color][/color]
event.[color=blue][color=green]
> > However, I seem to remember using a browser on Windows that didn't fire[/color]
> the[color=green]
> > event either. (Maybe an old version of Netscape or something.)
> > Additionally, has anyone on a Mac OS had problems with context-sensitive
> > menus employing this trick?
> >[/color]
>
> yes only yesterday you were informing a user that all he has to do is hod
> down the mouse button while he presses the enter button on the keyboard.
>
> Yo made a error, but in your quest to hide this you have attracted[/color]
attention[color=blue]
> to yourself
>[/color]

My initial method ONLY works on pages that only trap the right-click event
in IE and Mozilla (and possibly others). If you want to count that against
me, go ahead. I made a _huge_ mistake in assuming that this person was
trying to view a page that was trying to trap the right mouse click (like
many I have personally encountered). I am sorry, you may flame me at will.

Obviously, the OP isn't as interested in this thread as we are since he
never did tell us how the page was blocking his attempt to view the source.

A nice biproduct of our discussion is that a lot of other people have shared
their methods of access a stubborn web page's source. Not all is lost.

Many thanks for your (hopefully) helpful criticism,
Zac

**Zac Hester** · Jul 20 '05, 09:19 AM

Re: PrintWindow()

"Mosley Jones III" <me@info.gov.ma rs> wrote in message
news:3f1f4d68$2 @funnel.arach.n et.au...[color=blue]
>
> "Zac Hester" <news@planetzac .net> wrote in message
> news:3f1ecc95$1 @news.enetis.ne t...
>[color=green]
> >
> > Using the context menu on a web page element is a core function of the
> > browser and not something a web designer can control (unless you're[/color][/color]
using[color=blue]
> IE[color=green]
> > which does allow a web designer to override a lot of its basic
> > functionality).[/color]
>
>
> Ohhh so now you are changing your story?
>[/color]

In the English language there's such a thing as a modifying clause. A
person makes a statement that is supposed to state a broad, sweeping fact,
then the statement is refined to be more precise in meaning via a clause.
When I say, "All icecream tastes good (except for pralene)," I'm doing the
same thing. You start by making an absolute statement and follow it with
any notable exceptions. It allows you to get the details out of the way
without cluttering the overall meaning of a statement. If this seems to be
a subvertive tactic on my part, I apologize. My intentions were sincere.
[color=blue]
> I'm not interested in your second guesses. I really don't care
>[/color]

If it helps, there's a feature in "X-Newsreader: Microsoft Outlook Express
6.00.2800.1158" that allows you to block all the posts from a given person:

"Message" -> "Block Sender..." -> "Yes"

Just highlight one of my posts and block me. That should fix a lot of
things. You won't have to put up with my "second guesses" anymore. It's
apparent that there's nothing you can learn from me, so I can't think of a
reason why you haven't already blocked me.

Most sincerely,
Zac

**Mosley Jones III** · Jul 20 '05, 09:20 AM

Re: PrintWindow()

"Zac Hester" <news@planetzac .net> wrote in message
news:3f20040e$1 @news.enetis.ne t...[color=blue]
>
> "Mosley Jones III" <me@info.gov.ma rs> wrote in message
> news:3f1f4d69@f unnel.arach.net .au...[color=green]
> >
> > "Zac Hester" <news@planetzac .net> wrote in message
> > news:3f1ede82$1 @news.enetis.ne t...[color=darkred]
> > > "Lasse Reichstein Nielsen" <lrn@hotpop.com > wrote in message
> > > news:smoxf5uy.f sf@hotpop.com.. .
> > > > "Zac Hester" <news@planetzac .net> writes:
> > > >
> > > > > What are you labeling as "nonsense?" My method of subverting
> > > "right-click
> > > > > trapping" or his inability to view the source of a given web page?
> > > >
> > > > Your method, if I read him right.
> > > > Just write
> > > > <body oncontextmenu=" return false">
> > > > in a page and try your method. No pop-up dialog at all, works in[/color][/color][/color]
both[color=blue][color=green][color=darkred]
> > > > IE and Mozilla (and should be a hanging offense in real pages,[/color]
> > ofcourse).[color=darkred]
> > > >
> > > > He is, however, a little too confident in that method, since turning
> > > > off javascript will stop it cold. Who cares, though, there is no
> > > > functionality in the normal context menu that isn't available[/color][/color][/color]
through[color=blue][color=green][color=darkred]
> > > > the menu anyway.
> > >
> > > I saw that method on some hacker-ese page once. I found it funny[/color][/color][/color]
since[color=blue][color=green]
> > they[color=darkred]
> > > had all kinds of JavaScript traps that I learned how to use by looking[/color]
> > right[color=darkred]
> > > at their code. They even packaged up all their JavaScript in nice,
> > > easy-to-download external script files. It's been a while, but I'm[/color][/color]
> pretty[color=green][color=darkred]
> > > sure Konquerer (Gecko-based, I think) didn't fire the oncontextmenu[/color][/color]
> event.[color=green][color=darkred]
> > > However, I seem to remember using a browser on Windows that didn't[/color][/color][/color]
fire[color=blue][color=green]
> > the[color=darkred]
> > > event either. (Maybe an old version of Netscape or something.)
> > > Additionally, has anyone on a Mac OS had problems with[/color][/color][/color]
context-sensitive[color=blue][color=green][color=darkred]
> > > menus employing this trick?
> > >[/color]
> >
> > yes only yesterday you were informing a user that all he has to do is[/color][/color]
hod[color=blue][color=green]
> > down the mouse button while he presses the enter button on the keyboard.
> >
> > Yo made a error, but in your quest to hide this you have attracted[/color]
> attention[color=green]
> > to yourself
> >[/color]
>
> My initial method ONLY works on pages that only trap the right-click event
> in IE and Mozilla (and possibly others). If you want to count that[/color]
against[color=blue]
> me, go ahead. I made a _huge_ mistake in assuming that this person was
> trying to view a page that was trying to trap the right mouse click (like
> many I have personally encountered). I am sorry, you may flame me at[/color]
will.[color=blue]
>
> Obviously, the OP isn't as interested in this thread as we are since he
> never did tell us how the page was blocking his attempt to view the[/color]
source.[color=blue]
>
> A nice biproduct of our discussion is that a lot of other people have[/color]
shared[color=blue]
> their methods of access a stubborn web page's source. Not all is lost.
>
> Many thanks for your (hopefully) helpful criticism,
> Zac
>[/color]

No problems Zac

**OysterCracker** · Jul 20 '05, 09:20 AM

OP Apologies - was: PrintWindow()

>[color=blue]
> Obviously, the OP isn't as interested in this thread as we are since he
> never did tell us how the page was blocking his attempt to view the[/color]
source.[color=blue]
>[/color]

My apologies to the ng. I was interested, and got good early feedback
regarding a simple, suitable solution for me. This ng is a valuable resource
and I don't mean to abuse it. At the same time, my interest was in the
solution, not in how to bypass their block on the source code. This thread
quickly took a turn in that direction. The url was a secure financial site
that required passwords I was not willing to share, so I didn't see any
benefit in providing the url. I also had no intentions of starting WWIII...
if I had any spare valium, I'd be glad to share it but I need all I have.
Thanks again for the help.
~OC~

"Zac Hester" <news@planetzac .net> wrote in message
news:3f20040e$1 @news.enetis.ne t...[color=blue]
>
> "Mosley Jones III" <me@info.gov.ma rs> wrote in message
> news:3f1f4d69@f unnel.arach.net .au...[color=green]
> >
> > "Zac Hester" <news@planetzac .net> wrote in message
> > news:3f1ede82$1 @news.enetis.ne t...[color=darkred]
> > > "Lasse Reichstein Nielsen" <lrn@hotpop.com > wrote in message
> > > news:smoxf5uy.f sf@hotpop.com.. .
> > > > "Zac Hester" <news@planetzac .net> writes:
> > > >
> > > > > What are you labeling as "nonsense?" My method of subverting
> > > "right-click
> > > > > trapping" or his inability to view the source of a given web page?
> > > >
> > > > Your method, if I read him right.
> > > > Just write
> > > > <body oncontextmenu=" return false">
> > > > in a page and try your method. No pop-up dialog at all, works in[/color][/color][/color]
both[color=blue][color=green][color=darkred]
> > > > IE and Mozilla (and should be a hanging offense in real pages,[/color]
> > ofcourse).[color=darkred]
> > > >
> > > > He is, however, a little too confident in that method, since turning
> > > > off javascript will stop it cold. Who cares, though, there is no
> > > > functionality in the normal context menu that isn't available[/color][/color][/color]
through[color=blue][color=green][color=darkred]
> > > > the menu anyway.
> > >
> > > I saw that method on some hacker-ese page once. I found it funny[/color][/color][/color]
since[color=blue][color=green]
> > they[color=darkred]
> > > had all kinds of JavaScript traps that I learned how to use by looking[/color]
> > right[color=darkred]
> > > at their code. They even packaged up all their JavaScript in nice,
> > > easy-to-download external script files. It's been a while, but I'm[/color][/color]
> pretty[color=green][color=darkred]
> > > sure Konquerer (Gecko-based, I think) didn't fire the oncontextmenu[/color][/color]
> event.[color=green][color=darkred]
> > > However, I seem to remember using a browser on Windows that didn't[/color][/color][/color]
fire[color=blue][color=green]
> > the[color=darkred]
> > > event either. (Maybe an old version of Netscape or something.)
> > > Additionally, has anyone on a Mac OS had problems with[/color][/color][/color]
context-sensitive[color=blue][color=green][color=darkred]
> > > menus employing this trick?
> > >[/color]
> >
> > yes only yesterday you were informing a user that all he has to do is[/color][/color]
hod[color=blue][color=green]
> > down the mouse button while he presses the enter button on the keyboard.
> >
> > Yo made a error, but in your quest to hide this you have attracted[/color]
> attention[color=green]
> > to yourself
> >[/color]
>
> My initial method ONLY works on pages that only trap the right-click event
> in IE and Mozilla (and possibly others). If you want to count that[/color]
against[color=blue]
> me, go ahead. I made a _huge_ mistake in assuming that this person was
> trying to view a page that was trying to trap the right mouse click (like
> many I have personally encountered). I am sorry, you may flame me at[/color]
will.[color=blue]
>
> Obviously, the OP isn't as interested in this thread as we are since he
> never did tell us how the page was blocking his attempt to view the[/color]
source.[color=blue]
>
> A nice biproduct of our discussion is that a lot of other people have[/color]
shared[color=blue]
> their methods of access a stubborn web page's source. Not all is lost.
>
> Many thanks for your (hopefully) helpful criticism,
> Zac
>
>[/color]

PrintWindow()

PrintWindow()

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment