Hello,

We are experiencing problems with altering or adding filters in InfoAssist when using Google Chrome release version 80.0.3987.87, while release 79.0.3945.130 works fine.

This is currently causing issues for us in production WebFOCUS which is 8.1.05 on AIX.

When I try to revert back to the prior version of Chrome using properties it says there is nothing available. Other browsers can be used but this is our most popular one.

Is anyone else experiencing this issue?

Mike Long
Univ of Conntecticut

This message has been edited. Last edited by: FP Mod Chuck,

Look at the popup blocker.

Seems that now it is always activated and even adding as trusted site seems not to work.
Need to Allow popup instead of Blocked

quote:

Originally posted by MartinY:
Look at the popup blocker.

Seems that now it is always activated and even adding as trusted site seems not to work.
Need to Allow popup instead of Blocked

I've enabled Pop-ups and redirects in Edge Chromium yet the issue persists, cleared browser cache, restarted, nada.

Is there another setting involved?

Broken in new Edge too now that is has updated to v80.

IBI logic: Let's not use an actual html element like <select>. Let build it whole thing in a bunch of nested <div> elements that are POP-UPS!! Because it's only been know that pop-ups are a security risk since like what, 1999?

  
<div id="BiPopup-5475" class="bi-popup                                " style="user-select: none; white-space: nowrap; z-index: 1012882; left: 818px; top: 166px; width: 455px; height: 112px; visibility: hidden; display: none;"> 
   <div id="BiList-5477" class="bi-combo-box-list combo-box-list" tabindex="-1" style="outline: none; left: 0px; top: 0px; width: 455px; height: 112px;">
      <div id="BiComboBoxItem-3672" class="bi-list-item list-item list-item-selected list-item-lead " style="user-select: none; white-space: nowrap;">Constant</div>
      <div id="BiComboBoxItem-3674" class="bi-list-item list-item" style="user-select: none; white-space: nowrap; visibility: inherit;">Parameter</div>
      <div id="BiComboBoxItem-3675" class="bi-list-item list-item" style="user-select: none; white-space: nowrap; visibility: inherit;">Field</div>
   </div>
</div>

I opened a case with IBI Tech Support and:
Hello Mike,
Thank you for the detailed explanation. This is a known issue that has been reported to the development team. They are working actively right now to resolve this issue. I will link this case to that ticket and notify you immediately once I receive any updates/feedback from the division.
Best regards,

@Hallway:
I just tried Edge and I don't have the same issue as in Chrome. What specific version of Edge are you seeing this in?

quote:

Originally posted by BabakNYC:
@Hallway:
I just tried Edge and I don't have the same issue as in Chrome. What specific version of Edge are you seeing this in?

It wasn't happening in Edge at first for me either, until Edge updated to version 80. Just to clarify, I'm talking about The new Edge Chromium.

FYI - Altering the pop-up setting in Chrome version 80.0.3987.87 had no effect for me, the problem persisted, still unable to edit or add new filters in InfoAssist.

The same problem also occurs in our test WF8.2.06.13 environment, gen 134.

Had the same issue here. Support said it is a known issue with this version of chrome, they pushed a workaround to our cloud instance but i have no idea what it was. But you should be able to get help via support for it at least.

So, what is the #1 rule when assigning an ID attribute to an html element?

Here's a clue: https://developer.mozilla.org/...s/Web/API/Element/id

quote:

If the id value is not the empty string, it must be unique in a document.

And here's the console log when opening IA+ in Chrome and Edge v80:

ia:1 [DOM] Found 6 elements with non-unique id #dtpTextField: (More info: https://goo.gl/9p2vKq) 
    <input autocomplete=​"OFF" id=​"dtpTextField" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"visibility:​ hidden;​ height:​ 23px;​">​ 
    <input autocomplete=​"OFF" id=​"dtpTextField" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"visibility:​ hidden;​ height:​ 23px;​">​ 
    <input autocomplete=​"OFF" id=​"dtpTextField" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"visibility:​ hidden;​ height:​ 23px;​">​ 
    <input autocomplete=​"OFF" id=​"dtpTextField" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"visibility:​ hidden;​ height:​ 23px;​">​ 
    <input autocomplete=​"OFF" id=​"dtpTextField" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"visibility:​ hidden;​ height:​ 23px;​">​ 
    <input autocomplete=​"OFF" id=​"dtpTextField" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"visibility:​ hidden;​ height:​ 23px;​">​
ia:1 [DOM] Found 2 elements with non-unique id #metaDataSearchTxtFld: (More info: https://goo.gl/9p2vKq) 
    <input autocomplete=​"OFF" id=​"metaDataSearchTxtFld" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"border-style:​ none;​ font-family:​ Tahoma;​ font-size:​ 11px;​ color:​ grey;​ outline:​ none;​ left:​ 0px;​ top:​ 0px;​ width:​ 597px;​ height:​ 23px;​">​ 
    <input autocomplete=​"OFF" id=​"metaDataSearchTxtFld" class=​"bi-text-field text-field" tabindex=​"1" type=​"text" style=​"border-style:​ none;​ font-family:​ Tahoma;​ font-size:​ 11px;​ color:​ grey;​ outline:​ none;​ left:​ 0px;​ top:​ 0px;​ width:​ 0px;​ height:​ 23px;​">​

🤦

We have received a patch and have successfully resolved our issue as of this morning. We had to alter a .js file, remove a few others and replace a .jar file to make things work properly again.

Thank You!

quote:

Originally posted by MikeLong:
We have received a patch and have successfully resolved our issue as of this morning. We had to alter a .js file, remove a few others and replace a .jar file to make things work properly again.

Thank You!

Sad that we have to do this. That is BASIC html.

But what's even more sad that IBI is not proactively notifying all it's users about this fix. Instead it is waiting to react to users submitting a case. I think that since this is a known issue, the first thing should have happened is that every account manager sends an email to their accounts to notify of the issue, and the steps to correct. They should also be offering assistance to their accounts that need it. That's what I think "Award Winning Customer Service" should look like (maybe that's just me). But instead, all we get is... *cricketsChirping

I opened a case about this, too, but have not heard back yet for a fix. In the meantime, all my users are afraid to reboot because the Chrome update seems to be forced on a reboot.

An announcement about this was just posted on the main page on the techsupport site. The fix is heavily dependant on which version of WebFOCUS is in use so a case will need to be opened to get the appropriate fix

quote:

Originally posted by DWaybright:
I opened a case about this, too, but have not heard back yet for a fix. In the meantime, all my users are afraid to reboot because the Chrome update seems to be forced on a reboot.

I got a reply on my case that said all the info that I need is here: https://techsupport.informatio.../wbf/wbf_chrome.html and applying the patch will fix the issue. Yet the announcement says that the patch date is still three days away!! They also said that if I'm not ready to apply the patch (which dosen't exist yet) then I just need to use a different browser... Well guess what? It's breaking in the latest version of Edge now too.

Hallway

You can still get the patch before Monday separately, It will be included in any downloads of the software as of Monday. Please update your case to report it is happening with EDGE as well.

Indeed the patch fixes both Chrome and Edge Chromium.

quote:

Originally posted by BabakNYC:
Indeed the patch fixes both Chrome and Edge Chromium.

Now if we could get anyone at InfoResponse Live to share said patch with us.

I did see that there is some sort if infinite loop going on in the JavaScript that is incrementing the z-index value of the filter dialog box. So every time it increments, it redraws the filter dialog, thus eliminating anything you have tried to enter in any input element.

I opened a case yesterday and the initial response was to apply a maintenance release.
After I asked, they did provide a patch. (files and instructions that require renaming, replace, updating a few filenames)

I think the files might be release specific. Maybe if enough cases open they would consider a little more availability

It was an easy test. Make an IA report, drag a field to filter, click get values, nothing returns.

We did get our patch after specifically asking for the one for our release. My users are all happily working in Chrome again.