Proxomitron problem!

[Peter]

I have a weird but annoying problem: Proxomitron appears to add
scripts to web pages viewed on line. If I don't use a proxy, or bypass
Proxomitron, everything is normal but with Proxomitron active I get a
series of scripts added to web pages(see below). I have no idea what
this means but I don't like it. Sometimes they affect the appearance
of a page, but that's the least of my worries.
What causes this and what to do against it?

Peter


At the top of the page:

<SCRIPT>var PrxLC=new Date(0);var PrxModAtr=0;var PrxInst;
if(!PrxInst++) PrxRealOpen=window.open;function PrxOMUp(){PrxLC=new
Date();}function PrxNW(){return(this.window);} function
PrxOpen(url,nam,atr){ if(PrxLC){ var cdt=new Date();
cdt.setTime(cdt.getTime()-PrxLC.getTime()); if(cdt.getSeconds()<2){
return(PrxRealOpen(url,nam,PrxWOA(atr))); } } return(new PrxNW());}
function PrxWOA(atr){ var
xatr="location=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes";
if(!PrxModAtr) return(atr); if(atr){ var hm;
hm=atr.match(/height=[0-9]+/i); if(hm) xatr+="," + hm;
hm=atr.match(/width=[0-9]+/i); if(hm) xatr+="," + hm; }
return(xatr);}window.open=PrxOpen;</SCRIPT>
<!--//-->
<SCRIPT>PrxModAtr=1;</SCRIPT>
<!--//-->
<SCRIPT> function NoError(){return(true);} onerror=NoError; </SCRIPT>
<!--//-->
<SCRIPT> function moveTo(){return true;}function resizeTo(){return
true;}</SCRIPT>
<!--//-->
<SCRIPT> function setTimeout(x,y){return(null);} </SCRIPT>
<!--//-->
<SCRIPT> if (top.location != location){window.open(location.href);
window.close(); } </SCRIPT>

And at the bottom (but not always):

<!--//--><script>if(document.layers){document.captureEvents(Event.MOUSEUP);}document.onmouseup=PrxOMUp;</script>

 

[Josef W. Segur]

I have a weird but annoying problem: Proxomitron appears to add
scripts to web pages viewed on line. If I don't use a proxy, or bypass
Proxomitron, everything is normal but with Proxomitron active I get a
series of scripts added to web pages(see below). I have no idea what
this means but I don't like it. Sometimes they affect the appearance
of a page, but that's the least of my worries.
What causes this and what to do against it?

Those are simply the way that Proxomitron implements some of the
web page filters you have turned on. Read the documentation, turn
off any filters you don't want.

 

[Blinky the Shark]

I have a weird but annoying problem: Proxomitron appears to add
scripts to web pages viewed on line. If I don't use a proxy, or bypass
Proxomitron, everything is normal but with Proxomitron active I get a
series of scripts added to web pages(see below). I have no idea what
this means but I don't like it. Sometimes they affect the appearance
of a page, but that's the least of my worries. What causes this and
what to do against it?

It's how Proxo works. It's how it does the things you've told it to do.
If this bothers you, uninstall it.

 

[Peter]

It's how Proxo works. It's how it does the things you've told it to do.
If this bothers you, uninstall it.

Those are simply the way that Proxomitron implements some of the
web page filters you have turned on. Read the documentation, turn
off any filters you don't want.

Thanks for the replies. I guess I have to figure out which filters to
turn off and which filters affect web page appearance. I still don't
quite understand why it adds scripts to pages which don't have any
(such as my own, which are in simple html and css only).

Peter

 

[Aaron]

Thanks for the replies. I guess I have to figure out which filters to
turn off and which filters affect web page appearance. I still don't
quite understand why it adds scripts to pages which don't have any
(such as my own, which are in simple html and css only).

Proxomitron works by modifying the html from the webserver before passing
it to the browser to be displayed. This usually works by replacing the
offending html with some kind of filler.

BTW, this only affects the local copy you download when you read, it
doesnt affect the copy on the server in case you didnt know.

As for your specific querry, it's hard to answer, if we dont know the
exact ruleset you are using.

Peter

Aaron

 

[John Fitzsimons]

I have a weird but annoying problem: Proxomitron appears to add
scripts to web pages viewed on line.

< snip >

I have never had that happen, It might have helped had you told us
which version you use, but in any case I suggest you uninstall what
you have and do a fresh install. That should return you to "default"
settings and possibly fix things up.

Regards, John.

--
****************************************************
,-._|\ (A.C.F FAQ) http://clients.net2000.com.au/~johnf/faq.html
/ Oz \ John Fitzsimons - Melbourne, Australia.
\_,--.x/ http://www.aspects.org.au/index.htm
v http://clients.net2000.com.au/~johnf/

 

[Blinky the Shark]

There is no "offending html" in my webpages (nor do I use scripts).
Proxomitron can turn an invisible frameborder into a visible one,
which is very annoying. One wonders why it does that. How on earth can

It's not annoying to the user that prefers that.

one design web pages when even little programs like Proxomitron can
screw up the layout? It's difficult enough to make things look more or
less the same in different browsers.

Even more basically, users' browser settings (if they're astute enough
to have discovered that they *have* the ability to tweak their browsers)
can change the rendering of your markup. You can't force your "ideal
page" on them, even if they're not using a proxy like Proxo. You would
probably get some good observations regarding your question,
"How...screw up the layout?", if asked over at alt.html. Might ask them
about frames, too.

 

[Aaron]

There is no "offending html" in my webpages (nor do I use scripts).

Offending html does not just mean scripts. It can be anything from the way
your site uses frames ,the way it uses tables for layouts, css whatever the
user fancies. anything u do with your html, a enprising proxomitron user
can undo or change.

There are even filters floating around to customise popular sites like
yahoo etc.

Proxomitron can turn an invisible frameborder into a visible one,
which is very annoying. One wonders why it does that. How on earth can
one design web pages when even little programs like Proxomitron can
screw up the layout?

To you it screws up the layout, other people might want it that way.

It's difficult enough to make things look more or
less the same in different browsers.

Like it or not that's the way things are going, even without proxomitron,
web browsers like mozilla, Opera allows the users to ignore CSS, color
layouts and whatnot.

If you are obsessed with having 100% control over the appearance of your
website, you are going to have a hard time.

You made me curious enough to see what tags proxomitron (default out of box
settings) added to mine. It added quite a few at the end and at the top.
different from yours, but my display wasnt really affected.

Peter

Aaron

 

[R.L]

There is no "offending html" in my webpages (nor do I use
scripts). Proxomitron can turn an invisible frameborder
into a visible one, which is very annoying. One wonders why
it does that.

Of course, different people have different tastes and needs.
For example, one can set even just IE to ignore all the colors
and fonts defined by the web designer. Also, there are some
who have visual problems would zoom fonts to super big size,
which can also mess up the intended look of the page if the
designer does not have this in mind.

How on earth can one design web pages when
even little programs like Proxomitron can screw up the
layout? It's difficult enough to make things look more or
less the same in different browsers.

Anyhow, in case some would wonder, there are indeed a few
things that is generally considered as "undesirable" by many
people who would choose to use proxo in the first place.

- pop up, pop under, and other ads
- frames (some don't like it, so proxo put a bar on it so you
can resize it to see the main content), some filter can get
rid of your frame of all together.
- sounds
- moving pictures or animations, flash


Basically, a lot of tweaks that Proxo has is to make the
crucial "information" and "content" on the page become more
readable, for those who go to a site for just it content and
don't want to be distracted and wait for a long download.

Therefore, I have seen some webpages have two versions: a
plain version and a fancy version (e.g., Google News have a
text version, too). I think it is a great idea.

Just my 2cents

 

[Peter]

It's not annoying to the user that prefers that.

No one preferred that in this case. Proxomitron can alter the
appearance of a web page even if a user has not asked for it.

Even more basically, users' browser settings (if they're astute enough
to have discovered that they *have* the ability to tweak their browsers)
can change the rendering of your markup.

Yes, of course, if a user WANTS a different appearance, but that's not
the issue here.

You can't force your "ideal
page" on them, even if they're not using a proxy like Proxo.

LIke a wrote, that's not the issue here!

You would
probably get some good observations regarding your question,
"How...screw up the layout?", if asked over at alt.html. Might ask them
about frames, too.

I know what some of the more vociferous posters there think about
framesets and I am aware of their drawbacks too, but framesets are not
the subject of this thread.

Peter

 

[Aaron]

No one preferred that in this case. Proxomitron can alter the
appearance of a web page even if a user has not asked for it.

By choosing to run proxomitron out of the box, without any
configuration, the user has already implictly asked to do so. That is
what proxomitron does after all, alter webpages to fit a certain
preferance!

What most users do is to run proxomitron out of the box first, notice
stuff they like or dont like, customise and tweak it some more and
finally reaching their favourite settings.

If the user doesnt like what proxomitron does he can easily stop using
it.

Yes, of course, if a user WANTS a different appearance, but that's not
the issue here.

That is the issue here. See above. You personally as the webdesigner
might not like what proxomitron do out of the box with your website, if
so then tweak it to your liking, proxomitron is meant to be customised.

The default settings have being used by a lot of people, all without
problems, but it cant satisfy everyone...

LIke a wrote, that's not the issue here!

Like I wrote, that's the issue!

I know what some of the more vociferous posters there think about
framesets and I am aware of their drawbacks too, but framesets are not
the subject of this thread.

This I agree with. That remark was uncalled for.

Peter

Aaron

 

[Blinky the Shark]

By choosing to run proxomitron out of the box, without any
configuration, the user has already implictly asked to do so. That is
what proxomitron does after all, alter webpages to fit a certain
preferance!

What most users do is to run proxomitron out of the box first, notice
stuff they like or dont like, customise and tweak it some more and
finally reaching their favourite settings.

If the user doesnt like what proxomitron does he can easily stop using
it.

That is the issue here. See above. You personally as the webdesigner
might not like what proxomitron do out of the box with your website,
if so then tweak it to your liking, proxomitron is meant to be
customised.

The default settings have being used by a lot of people, all without
problems, but it cant satisfy everyone...

Like I wrote, that's the issue!

<irrelevant comment about frame removed>

This I agree with. That remark was uncalled for.

Reread the thread. Frames as an example of something that Proxo can
alter was *part of the discussion*, brought up by the *original poster*
-- I didn't just stick in a reference to them. All I did was suggest
alt.html as a source of information on their use, along with it being a
good place to get input on the "my markup versus user browser
configuration" that was the issue of which frame manipulation was *an
example*. There was nothing "uncalled for" or off-topic about that.

 

[Lurker]

Proxomitron is under construction...
http://www.proxomitron.info/

 

[Aaron]

Reread the thread. Frames as an example of something that Proxo can
alter was *part of the discussion*,

Actually, I perceived the discussion as the right of users to "screw" up
whatever the web designer intended to be displayed. That could occur to
any aspect of the web design not just frames.


brought up by the *original poster*

-- I didn't just stick in a reference to them.

I didnt say you did, i'm saying the way you made the comment. See later..

All I did was suggest
alt.html as a source of information on their use, along with it being a
good place to get input on the "my markup versus user browser
configuration" that was the issue of which frame manipulation was *an
example*. There was nothing "uncalled for" or off-topic about that.

This is what you wrote

"

You would
probably get some good observations regarding your question,
"How...screw up the layout?",

This is the comment i meant. If the webmaster wants to create frames with
a invisible frame border it's a design choice. Just as the vistor has a
choice to change it.

if asked over at alt.html. Might ask them about frames, too."

And as for the comments about asking about the merits of frames at
alt.html , well, let's just say that was certainly an attempt to weigh in
on the merits of frames versus non-frames (as the original poster
noted)...if you know (and i suspect you do *know*) the posters at
alt.html


PS I'm trying to stay out of the anti-faq, freeware verus commerical
alternatives etc threads because they don't add any value besides adding
to your visibility as a regular here. But.... some of them do have a
point.

PSSS Talk about uncalled comments

Aaron