Bug with firefox

GarryJones · Aug 31, 2008

I needed to hide and show som DIV sections,

There are many scripts on the net for this. I downloaded that allows
me to open a hidden DIV from inside a DIV than is itself hidden. This
accomplished I was pleased with my work.

That was until I saw the mess in Firefox which ignores everything I
tell it to do and opens all the DIVs regardless on load. Forgetting
the browser war jargon as to why Firefox would release a program that
doesn't work with common code I just need a way of doing this so it
works in Firefox AND MSIE and anything else out there.

function InsertContentmed(tid) {
if (
document.getElementById(tid).style.display == "none") {
document.getElementById(tid).style.display = "";
document.regfrms.cgfnm.focus();
}
else {
document.getElementById(tid).style.display = "none";
}
}

I am opening and closing a hidden DIV with a click call. (It opens it
when it is closed and it closes it when it is open, The other standard
way of doing this does not work for me as I need this to work from
withing a parent DIV that is itself opened by another Javascript
function.

Any and all help greatly appreciated

Garry Jones
Sweden

GarryJones · Aug 31, 2008

Solved!

I was having trouble earlier when I wrote this code so I changed a
couple of <DIV> tags to <p> tags. It was these that were faulting.

Firefox does not allow <p> tags to have a [ style="display: none" ]
component. Strange but true, when turned back to DIV it works
perfectly (even on MSIE). I dread to see my site on other browsers but
know I must......

Sorry to have disturbed you good people.....

However, a wider issue and OT but these differing Internet browsers
are a headache, rather like a country allowing people to drive on the
left and ride side of the road at the same time. I dont care which one
but wouldn't life be jollier if all the companies making browsers bar
one gave up and deleted their products? What's the point of more than
one?

Cheers
Garry Jones
Sweden

Thomas 'PointedEars' Lahn · Sep 1, 2008

GarryJones said:
Solved!

It only seems so. You have merely found a workaround to the problem as
caused by the insufficient analysis of it.

I was having trouble earlier when I wrote this code so I changed a couple
of <DIV> tags to <p> tags. It was these that were faulting.

Firefox does not allow <p> tags to have a [ style="display: none" ]
component.
Nonsense.

Strange but true, when turned back to DIV it works perfectly (even on
MSIE).

Which would indicate instead that either your markup or your script so far

Sorry to have disturbed you good people.....

Don't be sorry for *that*.

PointedEars

Arun · Sep 1, 2008

Firefox does not allow said:
Nonsense.

I agree with PointedEars. This claim is completely untrue. I wrote
the
following program and it works perfectly on all browsers I tested it
on.

...
<head>
...
<script type="text/javascript" language="JavaScript">
function toggle_container(id)
{
var container = document.getElementById(id);
container.style.display = (container.style.display == "")
? "none" : "";
}
</script>
</head>
<body>
...
<a href="javascript:void(0);"
onclick="toggle_container('some_text');">Toggle</a>
<p id="some_text" style="display:;">Hello there</p>
...
</body>
...

Which would indicate instead that either your markup or your script so far
is of poor quality, for <p style="display: none">...</p> works fine in my Fx
3.0.1 and all other CSS-capable UAs.

I'd like to add that I checked this code on IE(5,6,7,8b) and
Firefox(infancy-3.0),
after all, checking for browser compatibility is kinda part of my job.

Thomas 'PointedEars' Lahn · Sep 1, 2008

Arun wrote:
^^^^^^^^^^^
You are encouraged to shorten the attribution line to ease reading, but
please do not remove it.

Firefox does not allow <p> tags to have a [ style="display: none" ]
component.

Click to expand...

Nonsense.

Click to expand...

I agree with PointedEars. This claim is completely untrue. I wrote
the following program and it works perfectly on all browsers I tested
it on.

Even though it is error-prone and invalid ;-)

[...]
<script type="text/javascript" language="JavaScript">

^^^^^^^^^^^^^^^^^^^^^
The `language' attribute is deprecated and unnecessary nowadays.

[...]
<a href="javascript:void(0);"

^^^^^^^^^^^^^^^^^^^

You should not do that said:
onclick="toggle_container('some_text');">Toggle</a>

^
There is where the `return' statement belongs.

<p id="some_text" style="display:;">Hello there</p>

^^^^^^^^^
There you may have syntactically Valid markup, but not Valid CSS;
in a CSS property declaration, the property value is *required*.

<http://jigsaw.w3.org/css-validator/>

HTH

PointedEars

slebetman · Sep 1, 2008

No it wouldn't. Especially if the one that remains was IE.

Actually quite a few people think it would. Which is why there are
efforts to embed Mozilla in IE:

http://www.iol.ie/~locka/mozilla/control.htm

So now you can use xpath in IE -- HA!

SAM · Sep 2, 2008

GarryJones a écrit :

Firefox does not allow <p> tags to have a [ style="display: none" ]

That's new ?

My Fx.3 accepts this attribute with div or p

Arun · Sep 2, 2008

Thomas 'PointedEars' Lahn said:
Even though it is error-prone and invalid ;-)

I agree that the code is error-prone but is sufficient as an example.

^^^^^^^^^^^^^^^^^^^^^
The `language' attribute is deprecated and unnecessary nowadays.

Because the `language' attribute is deprecated, it doesn't mean that
it
might not work. It is mainly there for backward compatibility. People
still
use browsers that can not evaluate MIME-types in attribute values.

You should not do that said:
[...]
<a href="javascript:void(0);"

Click to expand...

^^^^^^^^^^^^^^^^^^^

You should not do that said:

onclick="toggle_container('some_text');">Toggle</a>

Click to expand...

^
There is where the `return' statement belongs.

Thanks for the link. I never knew all that stuff. I'll be sure to
clean up my act in days to come.

Thanks again,
Arun

Dr J R Stockton · Sep 2, 2008

In comp.lang.javascript message <[email protected]>, Mon,

1 Sep 2008 23:53:02 said:
Arun wrote:
^^^^^^^^^^^
You are encouraged to shorten the attribution line to ease reading, but
please do not remove it.

The OP is encouraged to ignore your various manias, Herr KontrolleFreak,
and to use a decently informative attribution line, as has (as you know)
been recommended by those who are mote intelligent, mature, and
experienced than yourself.

Thomas 'PointedEars' Lahn · Sep 3, 2008

Arun said:
I agree that the code is error-prone but is sufficient as an example.

There is a contradiction.

Because the `language' attribute is deprecated, it doesn't mean that
it might not work.

It makes no difference but in MSHTML with the value of "VBScript", and in
Mozilla with the value of "JavaScript1.2".

It is mainly there for backward compatibility.

Backwards compatibility to an obsolete standard that did not even define the
attribute in the first place? Think again.

People still use browsers that can not evaluate MIME-types in attribute values.

Name one.

Besides, it does not matter whether they can "evaluate MIME-types in
attribute values". Where the `type' attribute is ignored, an ECMAScript
implementation is the default (because at the time of shipping only
available) client-side scripting language. Where it is not, the HTML 4.01
standard was implemented.

PointedEars

getElementById ignored by Firefox	3	Sep 5, 2008
The Firefox browser does not display PDF with version 1.7	1	Sep 24, 2024
Maybe a bug in JavaScript?	2	Sep 2, 2022
Nesting Javascripts?	0	Aug 23, 2008
Help with code	0	Jun 12, 2022
Only one table shows up with the information	2	Mar 29, 2023
Help with my responsive home page	2	Dec 14, 2022
An unknown bug doesn't allow the quotes app to work. What's the issue?	3	Apr 23, 2023

Bug with firefox

GarryJones

GarryJones

Thomas 'PointedEars' Lahn

Arun

Thomas 'PointedEars' Lahn

slebetman

SAM

Arun

Dr J R Stockton

Thomas 'PointedEars' Lahn

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads