Illegal Invocation Error Written To Console When Executing Javascript After SPAC Fade Out (Doc ID 2230657.1)

Last updated on FEBRUARY 06, 2017

Applies to:

Oracle Live Help On Demand - Version N/A to N/A [Release ATG v1]
Information in this document applies to any platform.

Symptoms

On : N/A version, Rules Engine

Illegal Invocation Error Written To Console When Executing Javascript after SPAC Fade Out

While testing EE-7004 - Add a "run after fade" trigger for javascript (scheduled to be included in EE 17.01 Release), an error is written in the Console:

Uncaught TypeError: Illegal invocation atgsvcs.js:68
  at String. (atgsvcs.js:68)
  at q (atgsvcs.js:23)
  at ka (atgsvcs.js:67)
  at HTMLDivElement. (atgsvcs.js:47)
  at HTMLDivElement.d.complete (atgsvcs.js:2)
  at e.step (atgsvcs.js:5)
  at Array.f (atgsvcs.js:4)
  at atgsvcs.js:4

 
Setup:
--------
Page 2 Test Rule, ID: 7173037
Rule evaluation cycle = On Page Load
Recurrence = 10 seconds
Rule Evaluation max limit = 10

Do This:
Display RightNow Syndicated Proactive Chat with modal attribute set to Yes
Web Page Content: Fade Out
Delay = 20
Duration = 5
Run this JavaScript on fade out = document.getElementById("rn_DialogButton_rn_Dialog_0_1-button").click();
Element Property = Element ID
Element Property Value = myDiv

Events: Processing Rules
Stop Processing Rules = Current Rule

Meets conditions:
Web Page Title contains Page2

Steps to reproduce:
1 Open a browser and open the developer console
2. Navigate to http://missouri.rntdev.lan/autowebpage/aaron/1611-test/page2.html
3. Wait approximately 25 seconds

Observed Behavior: The following errors are written numerous times to the developer console and the javascript is not executed.

Uncaught TypeError: Illegal invocation atgsvcs.js:68
  at String. (atgsvcs.js:68)
  at q (atgsvcs.js:23)
  at ka (atgsvcs.js:67)
  at HTMLDivElement. (atgsvcs.js:47)
  at HTMLDivElement.d.complete (atgsvcs.js:2)
  at e.step (atgsvcs.js:5)
  at Array.f (atgsvcs.js:4)
  at atgsvcs.js:4

Expected Behavior: No errors would be written to the developer console and the javascript would be executed successfully.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, errors are written in the Console and the javascript is not executed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms