Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7678125
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T17:34:24+00:00 2026-05-31T17:34:24+00:00

We have a old Web Based application supported on browsers from IE6 to IE8

  • 0

We have a old Web Based application supported on browsers from IE6 to IE8 and javascript and css is very specific to the IE. Now we want to support IE9. In our javascript there are many syntaxes that are not supported in IE9, like accessing HTML attributes on element instances using dot (.) rather than setAttribute and getAttribute.

I was just wondering what is best way forward to support more browsers versions or support different browsers.

I was thinking like using jQuery to access non-standard features for all browsers or write a class called browser has method like getAttribute and then different class like IE7 and IE9 override this method on load in their specific way.

I want to use best way forward and approach used by users in such a scenrio.

setAttribute and GetAttribute are just simple examples there are many more for example to access the element reference we use document.all.elementName which is not supported in earlier versions of firefox etc. So how to convert all this code to Jquery or another library.
there are more problems then set and get attribute, the focus of question is what is best way to convert old javascript to supported javascript across all the browsers

Thanks

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T17:34:26+00:00Added an answer on May 31, 2026 at 5:34 pm

    If you have a large amount of code written specifically for IE < 9 that you wish to work in other browsers, you first need to identify all the IE specific code and then replace it with cross-browser code. I don’t think any particular library will help with that, in fact POJS is likely easier.

    For example, you can do a supervised replacement of document.all with document.getElementById, but you can’t do that with $ (where $ is from jQuery or Prototype or whatever).

    You’ll have issues using dot property access with non-standard attributes, but if they are set as properties, you’ll be fine (though it’s not a good idea to do so in principle).

    Incidentally, jQuery doesn’t “override” get/setAttribute, it has its own attr and prop methods.

    Ultimately, you’ll likely end up rewriting the whole thing from scratch. Just remember, don’t target particular browser versions, support standards and address non-standard behaviour where necessary using feature detection and a good fallback strategy.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have in here an old web application written in ASP.Net 2.0 + AJAX.
Scenario: old legacy code in rpg have to consume data from a new web
Age old question! When you have finished developing and testing your ASP.Net web application,
We have a Web Java based application running on JBoss with allowed maximum heap
We have a web application that only supports IE6 and above. It is an
I am rebuilding a web application from an old one with many inconsistencies. I
I am migrating a Perl-based web application to Rails. The old application stores dates
So, I have an web-based application that is using the Wicket 1.4 framework, and
I have a function within a custom CRM web application (old VB.Net circa 2003)
Here's the situation: I have a web-based ticket application, multiple users. One problem that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.