Member Avatar for server_crash

I'm testing something on an old version of netscape, specifically 4.7. Everythings fine except for my javscript function doesn't work because it says getElementById is not a function:

document.getElementById('ncp').src = "ncp" + pictureNum + ".jpg";


I've got many more of these type lines but it works fine in IE and FF. Is there something I can do to make this compatible with netscape browsers?

  • 5 Contributors
  • 5 Replies
  • 420 Views
  • 4 Years Discussion Span
  • Latest Post Latest Post by agb_bbsr

Dani AI

Generated

Short version: that error usually means one of three things — the document object you called it on doesn’t expose the standard DOM method, the element you expect doesn’t exist yet when the code runs, or your code relied on a non‑standard browser quirk that other engines don’t implement. The thread correctly points out that extremely old browsers behave differently and that dropping support is often the pragmatic choice (as and moved toward). For the long term, rely on the standard DOM API and defensive checks. (developer.mozilla.org)

Quick checklist and fixes to try now:

  1. Timing — run the code after the DOM is ready (place scripts at the end of the body or use the DOMContentLoaded pattern).
  2. Existence — confirm an element with the exact ID is present (IDs must be unique and, in some XML/XHTML contexts, case matters).
  3. Name vs ID — make sure you set an id attribute rather than depending on name (older IE historically matched names; modern browsers do not).
  4. Context — ensure you’re calling getElementById on the right document (not an iframe or a variable accidentally named document).
    Simple ready-state pattern:
    if (document.readyState === "loading") {
document.addEventListener("DOMContentLoaded", init);
} else {
init();
}

    Use console.log(document.getElementById('yourId')) while debugging to see whether it returns null. (developer.mozilla.org)

If supporting legacy engines is required, feature-detect and provide small fallbacks for only those cases; otherwise keep your code standards-based and add protective checks (verify the return value before accessing properties). and were right that maintaining ancient compatibility can be more work than it’s worth — modern browsers all implement the standard getElementById. For reference read the spec-style docs: getElementById and DOMContentLoaded. (developer.mozilla.org)

Recommended Answers

All 5 Replies

Member Avatar for tgreer

You'll have to navigate the hierarchy. For example, use the document.images collection.

I made the decision long ago that I simply wasn't going to worry myself, or add huge development overhead, to supporting old browers, particularly for corporate development projects and/or sites. Use a strict DOCTYPE, code to that standard, cut down on the fancy stuff, and use server-side code as much as possible.

Member Avatar for server_crash

I just decided to scrap the idea. I couldn't get anything to work without changing a bunch of code. I think to really get it to work you have to use layers with netscape, but it's just not worth it.

Thanks for the help!

Member Avatar for felgall

Netscape 6+ supports getElementById.
If you require support for Netscape 4 (about 1 visitor in 500 or less now) then you need to use document.layers instead just for those visitors and use getElementById for everyone else.

Member Avatar for shephunts

Yeah, the layers is the only way in netscape.

Member Avatar for agb_bbsr

document.getElementById("supplier_no").value = values_array[0];

java script: some times i get error as getElementById is invalid function or returns null. It works perfect in IE but not in Firefox. what is the reason...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.