Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Future consideration
Categories ClearQuest
Created by Guest
Created on Aug 12, 2019

Web Browser Usage not possible due to deprecated XMLHttpRequest

Due to deprecated XMLHttpRequest the usage of CQWeb in current Browser-Versions is no longer possible.

For further Information about XMLHttpRequests please see:
https://xhr.spec.whatwg.org/#the-open()-method

Idea priority High
RFE ID 135249
RFE URL
RFE Product Rational ClearQuest
  • Guest
    Nov 14, 2019

    Can you please give us any update on this? (change Headline; fix-version)

    How do we open the ticket for the 2nd issue?

  • Guest
    Oct 23, 2019

    Another Question:

    How do I open up the Ticket for the 2nd issue?
    Will I use the same way as opening the Ticket 135249?

    Thanks a lot for your help.
    Rica.

  • Guest
    Oct 23, 2019

    Thank you for your update.
    I havent received any Email-Notification about your updates.

    Our ClearQuest -Support Team will open a new Ticket für the 2nd issue (CQWeb will not load in Chrome 75).
    Please let us know in which version/fix the 1st issue will be solved.

    Thanks a lot for your Support.
    Rica.

  • Guest
    Oct 22, 2019

    We will change the headline of this RFE to "Remove Synchronous XMLHttpRequest in CQWeb" and accept it, as a result of the analysis for 1st issue.

    If you still cannot load CQWeb in Chrome, please open a ticket to have our support engineer help you with that.

  • Guest
    Sep 23, 2019

    Any updates? For 2nd issue, would you like to open a ticket to have our support engineer help you with that?
    We are looking forward to your response. Thank you.

  • Guest
    Sep 18, 2019

    Thanks for the feedback. After checking the screenshot for Chrome, I see there are two different issues.

    1. The warning of Synchronous XMLHttpRequest is being deprecated is true, but it's just a warning and XMLHttpRequest still remains. There is indeed no direct evidence suggesting that it'll be removed anytime soon, especially considering number of sites and technologies removal of the feature would affect. So don't worry about that in future there will be no current Browser-Version available to use CQWeb.

    2. CQWeb does support the latest version of Chrome. We've tried Chrome 76, 75 and CQWeb can load successfully. Back to your problem that while using the current Chrome Version 75, the CQWeb will not load, the real errors in the Chrome console is ERR_NAME_NOT_RESOLVED when requesting CQWeb scripts.
    ERR_NAME_NOT_RESOLVED is a common Chrome error that users experience at random. Please ask your IT admin or see this page for kinds of solutions.
    https://www.addictivetips.com/web/fix-the-err_name_not_resolved-chrome-error/

    So CQWeb works as usual in the latest versions of Firefox and Chrome and you could continue to use it.
    If you'd like, we could accept this RFE, but change the headline as "Remove synchronous XMLHttpRequest in CQWeb".
    Please let us know your further feedback. Thanks.

  • Guest
    Sep 4, 2019

    1. We are using the following versions:
    Client application: 9.0.1.5 FP5 or 9.0.1.6 FP6
    Websphere App Server: 9.0.0 FP10 or FP11
    Http Server: 9.0.0 FP10 or FP11

    2. The problem occurs when using the CQ weblink. When requesting the URL one can see the following messages in the developer consoles of Firefox and Chrome. Firefox warns against the usage of synchronous XMLHttpRequests, but despite loads the website. Chrome also shows a warning, but does not load the website. Chrome simply shows a blank page. You can also see the behaviour in the attached screenshots.
    Please see also:
    https://stackoverflow.com/questions/30876093/will-chrome-and-other-browsers-drop-support-for-synchronous-xmlhttprequest

  • Guest
    Sep 4, 2019

    Attachment (Description): Chrome warning against use of synchronous XMLHttpRequest

  • Guest
    Sep 4, 2019

    Attachment (Description): Firefox warns against use of synchrounos XMLHttpRequests

  • Guest
    Aug 27, 2019

    This request lacks sufficient information for us to evaluate it. Could you answer the following questions?

    1. What's the version of CQ you are using?
    2. Can you elaborate how CQWeb does not load in Chrome 75? Does the issue happen when you access CQWeb link or use REST API, OSLC?