Re: CSS puts in extra space ... why?

On Aug 4, 8:38 am, "Beauregard T. Shagnasty"
<a.nony.m... (AT) example (DOT) invalid> wrote:

RichardL wrote:
With Ed Mullen's help, I overcame my Comcast.net problems and have
now posted a version of my Preliminary Accordion Menu page on
http://home.comcast.net/~captqueeg/9...ordionMenu.htm.

Nothing happens when JavaScript is disabled or stripped by a corporate
firewall. That's like turning your web server off for a month every
year. (~10% of visitors can't navigate your site at all.)

The .htm file references .js and .css files. I wonder whether anyone
can see the sources for these auxiliary files, which may often be the
cause of authoring problems.

Not sure what you are asking... sure, they can be "seen".http://home.comcast.net/~captqueeg/9...tyleSheets.css

--
-bts
-Motorcycles defy gravity; cars just suck

Hi Beauregard,

Thanks for responding.

Not sure what you are asking... sure, they can be ?seen".
http://home.comcast.net/~captqueeg/9...MenuScripts.js

My mistake. I tried the ....js address yesterday and got nothing.
Today, it worked (i.e., its text was displayed) for me just as I
originally hoped and you expected.

My error probably was I pumped that URL into my IE7 browser, and it
and Comcast.net don't play well together. BTW, I was working on this
at ~1 a.m. and was hallucinating from sleep deprivation :-)

Nothing happens when JavaScript is disabled

Not true in this instance. On Ed's excellent advice, I turned off
JS in IE, the infinite loop in Comast.net's homepage ceased and I was
able to see that home page. (I had the same problem with my Firefox 2
browser.)

Furthermore, Ed told me he used SeaMonkey. I tried that browser,
which to my surprise worked perfectly on my system. That allowed me
to log on to Comcast.net, create a secondary account that will accept
no email, and create a personal web page which uses the latter
account. (The secondary account will protect me from spam as I
publish the PWP address from time to time.)

I don't know if I'll ever learn the real cause of the Comcast.net
problem on my machine. I find their tech support to be useless --
nice people, but not the sharpest arrows in the quiver. But no
matter: I've now got full functionality for my purposes.

Again, thanks for your response.

Best wishes,
Richard

Beauregard T. Shagnasty wrote:

RichardL wrote:

Furthermore, Ed told me he used SeaMonkey. I tried that browser,
which to my surprise worked perfectly on my system. That allowed me
to log on to Comcast.net, ...

It isn't SeaMonkey that allowed the page to work, it's the fact that you
probably have JavaScript disabled in SeaMonkey.

The comcast.net main page fails (goes into constant loop of some sort)
due to the JavaScript error, and does it in any browser with JavaScript
enabled.

I don't know if I'll ever learn the real cause of the Comcast.net
problem on my machine. I find their tech support to be useless --
nice people, but not the sharpest arrows in the quiver. But no
matter: I've now got full functionality for my purposes.

It isn't your machine. It's the web site with the problem.

I tried to use their "Contact Us" link, but it wants to dump a dozen
cookies on my browser(s) so I gave up on that. You're the subscriber;
you should let them know about the problem. Frankly, I'm surprised they
haven't already been notified that 90% of their visitors can't go to the
site.

The issue is not javascript, nor the browser compatibility. I just
tested it using SeaMonkey, Firefox, Opera and IE7. You need to allow
cookies on the site or it simply sits there looping as it tries to load.
Dumb design but that appears to be all it is.

--
Ed Mullen
http://edmullen.net
http://mozilla.edmullen.net
http://abington.edmullen.net
Don't bother me. I'm living happily ever after.

On Aug 4, 1:46 pm, "Beauregard T. Shagnasty"
<a.nony.m... (AT) example (DOT) invalid> wrote:

Ed Mullen wrote:
The issue is not javascript, nor the browser compatibility. I just
tested it using SeaMonkey, Firefox, Opera and IE7. You need to allow
cookies on the site or it simply sits there looping as it tries to
load. Dumb design but that appears to be all it is.

Ah, yes. My browsers refuse cookies by default, but it did work with
JavaScript disabled. It appears it's the JavaScript that sets all the
cookies, so if JavaScript is ON and cookies are accepted it works, and
if JavaScript is OFF, there is no "checking for cookies." Yes, a dumb
design; the main page dumped 16 cookies on my browser.

--
-bts
-Motorcycles defy gravity; cars just suck

Hi Ed and Beauregard,

My Firefox 2 had both JavaScript enabled and Cookies enabled.

=== Details
In Firefox 2 under Tools/Options:

Under Privacy/Cookies I've got:
Accept cookies from sites: checked
Keep until: ask me every time
Exceptions:
Comcast.net not listed
72.3.134.85: blocked
72.32.204.230 blocked

I don't know if those explicit addresses have anything to do with
Comcast.net

Under Content I've got:
Enable javascript: checked
=== End details

Aside from the above evidence, Firefox consistently tells me that
site "X" wishes to store a cookie and gives me options like, OK, OK
for session, Deny.

One more data point. I can access to Comcast.net, log on, etc. when I
run IE (5, I think) on my server, which runs Windows 2003 Server.
I've got it disconnected right now because I only when I'm testing
networking issues.

Another data point. At Ed's suggestion, I ran Firefox 2 in safe
mode, but Comcast.net still did its infinite-loop trick.

I pretty happy just using SeaMonkey for accessing Comcast.net, logging
in, and managing my personal web pages. Having that has made me a
happy camper.

As always, thank for addressing my problem and educating me on the
ways it might be investigated. Most of thanks to Ed for giving the
convenience of managing my PWP from my workstation.

Regards,
Richard

On Aug 4, 9:55 pm, RichardL
<RichardDummyMailbox58... (AT) USComputerGurus (DOT) com> wrote:

On Aug 4, 1:46 pm, "Beauregard T. Shagnasty"



a.nony.m... (AT) example (DOT) invalid> wrote:
Ed Mullen wrote:
The issue is not javascript, nor the browser compatibility. I just
tested it using SeaMonkey, Firefox, Opera and IE7. You need to allow
cookies on the site or it simply sits there looping as it tries to
load. Dumb design but that appears to be all it is.

Ah, yes. My browsers refuse cookies by default, but it did work with
JavaScript disabled. It appears it's the JavaScript that sets all the
cookies, so if JavaScript is ON and cookies are accepted it works, and
if JavaScript is OFF, there is no "checking for cookies." Yes, a dumb
design; the main page dumped 16 cookies on my browser.

--
-bts
-Motorcycles defy gravity; cars just suck

Hi Ed and Beauregard,

My Firefox 2 had both JavaScript enabled and Cookies enabled.

=== Details
In Firefox 2 under Tools/Options:

Under Privacy/Cookies I've got:
Accept cookies from sites: checked
Keep until: ask me every time
Exceptions:
Comcast.net not listed
72.3.134.85: blocked
72.32.204.230 blocked

I don't know if those explicit addresses have anything to do with
Comcast.net

Under Content I've got:
Enable javascript: checked
=== End details

Aside from the above evidence, Firefox consistently tells me that
site "X" wishes to store a cookie and gives me options like, OK, OK
for session, Deny.

One more data point. I can access to Comcast.net, log on, etc. when I
run IE (5, I think) on my server, which runs Windows 2003 Server.
I've got it disconnected right now because I only when I'm testing
networking issues.

Another data point. At Ed's suggestion, I ran Firefox 2 in safe
mode, but Comcast.net still did its infinite-loop trick.

I pretty happy just using SeaMonkey for accessing Comcast.net, logging
in, and managing my personal web pages. Having that has made me a
happy camper.

As always, thank for addressing my problem and educating me on the
ways it might be investigated. Most of thanks to Ed for giving the
convenience of managing my PWP from my workstation.

Regards,
Richard

I didn't say one thing clearly. Here's my improved statement:

Aside from the above evidence, and aside from Comcast.net, Firefox
consistently tells me whenever site "X" wishes to store a cookie and
gives me options like, OK, OK for session, Deny.

I hope that's clearer.
--
R