Closed Bug 30226 Opened 25 years ago Closed 25 years ago

invalid rendering - missing items

Categories

(Core :: DOM: Core & HTML, defect, P3)

defect

Tracking

()

VERIFIED INVALID

People

(Reporter: tomas_brixi, Assigned: danm.moz)

References

()

Details

Attachments

(2 files)

invalid rendering of shared folders tree can't download/upload files - corresponding menu not rendered
Log into the site as _mozilla, password mozilla. You get a JS error, so I'm reassigning to DOM0, since this works on NS 4.7.
Assignee: troy → vidur
Component: Layout → DOM Level 0
Keywords: 4xp
QA Contact: petersen → desale
this should be marked as new then... please remember that
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
1) Invalid rendering is result of border=noborder attribute setting in <img> tag ('noborder' keyowrd doesn't work but works as DOM0 in NS and IE) It should be equivalent to border=0 (which does work) 2) Upload /download function on the site is driven by some crazy obfusticated javascript code. I don't get a JS error, but the menu functions don't render (it shows only blank page in the frame). I'll continue tracing the code until I figure out why the frame isn't loading correctly. (And upload a second test case soon...)
The reason for the blank frame (shared folders tree) is that the name of the frame is "menubar" and that conflicts with the navigator.menubar property. This might be a dup of bug 31378 but since that deals with an other property I wont mark it a dup. Over to danm@netscape.com.
Assignee: vidur → danm
Status: ASSIGNED → NEW
OS: Windows 98 → All
Hardware: PC → All
Hmmmm. I can't get a DNS resolution on www.freedrive.com, and I don't seem to be having network problems. So I can't try this, but jst's comment above leads me to believe this is just invalid HTML. I'm not sure about navigator.menubar, but there is a window.menubar property. I imagine that's what he's talking about. menubar is a read-only property of the window object, and you can't bend it to your will. If that's the problem, you just need to change your source to use a different identifier name, one that's not reserved. Like I said, I can't get to the test site right now, so I may be completely off. If you reopen, breaking the problem down to a little bit of simple HTML and/ or JS and including it in the bug report would be very helpful.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Invalid name for frame. Marking verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: