Closed stevekram closed 1 year ago
Hi Steve. Please see if answers/workarounds on the FAQ page addresses this issue for you:
https://www.ssa.gov/accessibility/andi/help/faq.html#lby-wontLaunch
John,
Since we can successfully run ANDI on the “R”ome version of ServiceNow (verified in various browsers) but not “T”okyo, we feel we’ve eliminated CSP and Huge Test Page as potential causes. The JavaScript “favelet test” runs successfully, but we did note one new “Uncaught SyntaxError” when we launch ANDI.
@.*** We’ve verified this does NOT appear in the previous ServiceNow environment.
Hopefully this helps.
Steve Kram
From: John Cotter @.> Sent: Tuesday, January 17, 2023 8:37 AM To: SSAgov/ANDI @.> Cc: Steve Kram @.>; Author @.> Subject: Re: [SSAgov/ANDI] ANDI not functioning on ServiceNow "Tokyo" release (Issue #184)
Hi Steve. Please see if answers/workarounds on the FAQ page addresses this issue for you:
https://www.ssa.gov/accessibility/andi/help/faq.html#lby-wontLaunch
— Reply to this email directly, view it on GitHubhttps://github.com/SSAgov/ANDI/issues/184#issuecomment-1385434907, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5HV4QFTJBEZUVSA4X47JPLWS2N65ANCNFSM6AAAAAAT2YLOJM. You are receiving this because you authored the thread.Message ID: @.**@.>>
Can you please provide the error info (line number) for the syntax issue?
John,
Clicking the error message’s hot link marks line 7 of VM12321 9289854533f1d2dd3c7cd298d8908667.jsdbx
//code// import {lodash as TEMPlodash_4_17_4} from '/uxasset/externals/js-common-mega/bundled-assets.jsdbx';
@.***
From: John Cotter @.> Sent: Tuesday, January 17, 2023 9:04 AM To: SSAgov/ANDI @.> Cc: Steve Kram @.>; Author @.> Subject: Re: [SSAgov/ANDI] ANDI not functioning on ServiceNow "Tokyo" release (Issue #184)
Can you please provide the error info (line number) for the syntax issue?
— Reply to this email directly, view it on GitHubhttps://github.com/SSAgov/ANDI/issues/184#issuecomment-1385474326, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5HV4QFEB5J2D2FNDOEZHN3WS2RETANCNFSM6AAAAAAT2YLOJM. You are receiving this because you authored the thread.Message ID: @.**@.>>
That isn't a reference to anything that ANDI is using. I would assume that error might be present before ANDI is launched.
If you've already ruled out presence of iframes by following the FAQ, then the other thing that may cause the issue is if the page is rendered using shadow DOM. At this time, ANDI cannot detect shadow DOM content.
John,
I carefully re-executed the iframes work-around actions, and am now able to operate ANDI on the “T”okyo version of ServiceNow. 😊
Do we forever need to apply this work-around, or is there a update planned for ANDI that will handle ServiceNow’s iframes implementation?
Thanks.
Steve K.
From: John Cotter @.> Sent: Tuesday, January 17, 2023 9:14 AM To: SSAgov/ANDI @.> Cc: Steve Kram @.>; Author @.> Subject: Re: [SSAgov/ANDI] ANDI not functioning on ServiceNow "Tokyo" release (Issue #184)
That isn't a reference to anything that ANDI is using. I would assume that error might be present before ANDI is launched.
If you've already ruled out presence of iframes by following the FAQ, then the other thing that may cause the issue is if the page is rendered using shadow DOM. At this time, ANDI cannot detect shadow DOM content.
— Reply to this email directly, view it on GitHubhttps://github.com/SSAgov/ANDI/issues/184#issuecomment-1385490754, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5HV4QFQNKP6XOZ5RNU6RF3WS2SK5ANCNFSM6AAAAAAT2YLOJM. You are receiving this because you authored the thread.Message ID: @.**@.>>
Unfortunately, there isn't a way with ANDI to make this more streamlined. It's a limitation of what abilities browsers allow for externally executed scripts.
We understand. Thanks for checking, John.
Steve K. From: John Cotter @.> Sent: Tuesday, January 17, 2023 10:34 AM To: SSAgov/ANDI @.> Cc: Steve Kram @.>; Author @.> Subject: Re: [SSAgov/ANDI] ANDI not functioning on ServiceNow "Tokyo" release (Issue #184)
Unfortunately, there isn't a way with ANDI to make this more streamlined. It's a limitation of what abilities browsers allow for externally executed scripts.
— Reply to this email directly, view it on GitHubhttps://github.com/SSAgov/ANDI/issues/184#issuecomment-1385610629, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5HV4QBBDD3Q6UIZDHUH4HTWS23WTANCNFSM6AAAAAAT2YLOJM. You are receiving this because you authored the thread.Message ID: @.**@.>>
Hello, Our organization recently updated one of their ServiceNow environments from "Rome" to "Tokyo" (see https://www.servicenow.com/community/now-platform-articles/servicenow-versions/ta-p/2312014). ANDI works successfully on the older "Rome" in both Chrome and Firefox, but results in a blank locked-up session using "Tokyo". This is repeatable in current versions of Chrome, FireFox, and Edge. We see no indications why activating ANDI results in the ServiceNow screen becoming unresponsive. Screen capture shows ANDI functionality on "Rome" ServiceNow page, and the same page when activating ANDI using ServiceNow "Tokyo".
Thanks.
Steve![ANDI-servicenow screen captures](https://user-images.githubusercontent.com/122641984/212406252-4f963391-41e3-459b-b31a-184e19e760d3.png)