Closed
Bug 369415
Opened 19 years ago
Closed 19 years ago
Replacing "display:none;" with "overflow: hidden; height: 0px;"
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: bryan, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Firefox is replacing "display:none" with a new div and other style tags. This breaks my ability to unset the styling with JavaScript. View Source lies about what is actually there.
Reproducible: Always
Steps to Reproduce:
1. Go To Link
2. View source in FireBug.
Actual Results:
http://darkrockstr.com/files/FFDisplayBug.png
Comment 1•19 years ago
|
||
If I remove the following from the HTML source:
window.addEvent('domready', function()
{
....
});
then the extra DIV wrapper is not there.
The element is added by http://darkrockstr.com/Vinte/js/moo.js
probably as part of the Fx.Slide() or Fx.Style() calls.
DOM Inspector displays the DOM.
View Source displays the markup source text.
-> INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Comment 2•19 years ago
|
||
Oh, you were using FireBug, not DOM Inspector. FireBug is also displaying
the DOM tree rather than the source text...
| Reporter | ||
Comment 3•19 years ago
|
||
It works in Safari and in most IE. I do see that it's MooTools that is creating that div but why would it work in some browsers and not others?
Resolution: INVALID → WONTFIX
| Reporter | ||
Comment 4•19 years ago
|
||
Apparently it's a bug somewhere with replacing styles with JS in Firefox.
Resolution: WONTFIX → INVALID
Comment 5•19 years ago
|
||
No. There is no bug in Firefox here.
The JS code does one thing for Firefox and something completely different
for other UAs. For Firefox the JS inserted the element you are having
problems with. Complain to however wrote the JS code.
You need to log in
before you can comment on or make changes to this bug.
Description
•