-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ANDI still not working in Chrome #257
Comments
Do you see an error in the F12 dev tools console? |
Hi John, I do not see an error in the dev tools console.
Susan Supcoe
***@***.***
Accessibility / Section 508
www.boozallen.com<http://www.boozallen.com>
From: John Cotter ***@***.***>
Sent: Tuesday, December 31, 2024 10:07 AM
To: SSAgov/ANDI ***@***.***>
Cc: Supcoe, Susan [USA] ***@***.***>; Author ***@***.***>
Subject: [External] Re: [SSAgov/ANDI] ANDI still not working in Chrome (Issue #257)
Do you see an error in the F12 dev tools console? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. Message ID: <SSAgov/ANDI/issues/257/2566520841@ github. com>
Do you see an error in the F12 dev tools console?
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/SSAgov/ANDI/issues/257*issuecomment-2566520841__;Iw!!May37g!NogbGrgXF4nRbpfzFN1pxQkre9xccSogaYfG9WCviZxi4gZYRE7iN5_pTMi4zy052VO1m5meCn-O4wQdwGkG4aty$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BNV7LSLBDK2QLR4VJGYMV6L2IKXHNAVCNFSM6AAAAABTSRLZPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGUZDAOBUGE__;!!May37g!NogbGrgXF4nRbpfzFN1pxQkre9xccSogaYfG9WCviZxi4gZYRE7iN5_pTMi4zy052VO1m5meCn-O4wQdwCF3uNhD$>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Please try checking if favelets are blocked by following the steps here: |
Hi John,
I did the steps below and it appears that favelets are blocked. Is that something I can enable myself?
Thanks,
Susan
Susan Supcoe
***@***.***
Accessibility / Section 508
www.boozallen.com<http://www.boozallen.com>
From: John Cotter ***@***.***>
Sent: Tuesday, December 31, 2024 10:36 AM
To: SSAgov/ANDI ***@***.***>
Cc: Supcoe, Susan [USA] ***@***.***>; Author ***@***.***>
Subject: [External] Re: [SSAgov/ANDI] ANDI still not working in Chrome (Issue #257)
Please try checking if favelets are blocked by following the steps here: https: //www. ssa. gov/accessibility/andi/help/faq. html#wontLaunch — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because
Please try checking if favelets are blocked by following the steps here:
https://www.ssa.gov/accessibility/andi/help/faq.html#wontLaunch<https://urldefense.com/v3/__https:/www.ssa.gov/accessibility/andi/help/faq.html*wontLaunch__;Iw!!May37g!PSCLyIjCTWF33DRf8j4xBynr002BzNYwJYALue2vSSae9cKIBk490-FfUeACqJttSuNJKoigX7VqqMbj1nvR8bIx$>
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/SSAgov/ANDI/issues/257*issuecomment-2566541157__;Iw!!May37g!PSCLyIjCTWF33DRf8j4xBynr002BzNYwJYALue2vSSae9cKIBk490-FfUeACqJttSuNJKoigX7VqqMbj1s2GdrRz$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BNV7LSNGMSIF6LVL6NFN4RL2IK2UZAVCNFSM6AAAAABTSRLZPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGU2DCMJVG4__;!!May37g!PSCLyIjCTWF33DRf8j4xBynr002BzNYwJYALue2vSSae9cKIBk490-FfUeACqJttSuNJKoigX7VqqMbj1ljbTOON$>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
|
Unfortunately this is a browser security setting that was probably turned on by a system admin. You will need to discuss with that person to express your need and possible exception. This seems to be a problem that other ANDI lovers are experiencing in other fed agencies, so any additional guidance you can provide on resolving this would be appreciated by the community. |
Has there been any resolution to this issue? Using a government issued device, ANDI is not usable (won't launch) when testing in Chrome, which is recommended.
The text was updated successfully, but these errors were encountered: