Cannot Login to AT&T Email

For support with specific websites

Moderator: trava90

Forum rules
Please always mention the name/domain of the website in question in your topic title.
Please one website per topic thread (to help keep things organized). While behavior on different sites might at first glance seem similar, they are not necessarily caused by the same.

Please try to include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
  1. Clear any current output
  2. Navigate or refresh the page in question
  3. Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
Locked
pshipwrite
Apollo supporter
Apollo supporter
Posts: 39
Joined: 2018-04-18, 21:34

Cannot Login to AT&T Email

Unread post by pshipwrite » 2023-03-24, 18:58

I cannot login to AT&T Email. Unfortunately, only those with an AT&T email account can replicate this issue. Here are the step-by-step instructions to replicate the issue.

1. Navigate to website https://currently.att.yahoo.com/
2. Select Mail in the upper left corner of screen.
3. Enter your User ID, which is your email address, and Password and press the Sign in button.
4. The following screen will prompt you to send a code to your cell phone to confirm your identity (two factor authentication). Press the Send code button.
5. The next screen prompts you to Enter (the) code. I enter the six digit code and attempt to press the Submit button. I noticed the Submit button is grayed out until the six digit code is entered. Unfortunately, the Submit button cannot be pressed successfully. I can successfully press the Cancel button which asks "Are you sure you want to cancel? You'll have to sign in again and start over." The two options are Yes and No with Yes selected as the default.

Below I have copied all the text from the Web Console and Error Console. Any help in resolving this issue would be greatly appreciated. Until I can resolve this issue, I will have to access my AT&T email from a chrome browser. I would be interested to know if other AT&T email users are having similar issues.

Web Console

Code: Select all

detmScriptLoader - Governance prescribed Legacy mode is retired for this page.  
detm-container-hdr.js:8:80077
Adobe Solutions: governance does not allow delayed load od detm components  
detm-container-hdr.js:8:76582
----------  
detm-container-hdr.js:8:78255
detmScriptLoader - prod version: 2561  
detm-container-hdr.js:8:78281
detm scripts were loaded asynchronously because the application has overridden the default setting  
detm-container-hdr.js:8:78363
----------  
detm-container-hdr.js:8:78380
detmScriptLoader - Governance prescribed Legacy mode is retired for this page.  
detm-container-hdr.js:8:80077
detmScriptLoader - load delayed for (Adobe DTM) trigger: loadAnalytics  
detm-container-hdr.js:8:90734
detmScriptLoader - loading (and initializing): quantum-att.js start: 14:25:24.24 stop: 14:25:24.86 elapsed: 62ms  
detm-container-hdr.js:8:84030
Adobe solutions: error - could not load script quantum-att.js  
detm-container-hdr.js:8:84538
detmScriptLoader - loading (and initializing): ssaf-uc.js start: 14:25:24.86 stop: 14:25:24.108 elapsed: 22ms  
detm-container-hdr.js:8:84030
loadFile: error - could not load DFA script  
ssaf-uc.js:2:28288
DFA Success response data error { target: <script>, isTrusted: true, srcElement: <script>, eventPhase: 0, bubbles: false, cancelable: false, defaultPrevented: false, composed: false, timeStamp: 790, cancelBubble: false, originalTarget: <script> }  
ssaf-uc.js:2:43210
httpclient: 14:25:27.138: Warning -> SSAF UC MISSING IDSE_STACK MISSING  
ssaf-uc.js:2:3310
httpclient: 14:25:27.142: Warning -> SSAF UC MISSING IDSE_STACK MISSING  
ssaf-uc.js:2:3310
HALOReportingBridge creating bridge.  
halo-application-edm-bridge.js:1:5306
HALOReportingBridge created Object { checkForHaloLoginEventNeeded: checkForHaloLoginEventNeeded(), ACCOUNT_TYPE_WIRELESS: "WLS", ACCOUNT_TYPE_WIRELINE: "WLN", ACCOUNT_TYPE_UVERSE: "UVS", ACCOUNT_TYPE_DIRECTVNOW: "DIRECTVNOW", ACCOUNT_TYPE_WATCHTV: "WATCHTV", ACCOUNT_TYPE_ATTTV: "ATTTV", ACCOUNT_TYPE_DIRECTV: "SAT" }  
halo-application-edm-bridge.js:1:6527
Halo.C Bridge script loading is successfull!  
detm-container-hdr.js:8:65252
js_gb_adc :: no configuration found for this page, so footer ads not activated.../dynamic/iamLRR/LrrController  
detm-container-hdr.js:8:63397
js_gb_adc :: att monetization master config loading failed... ReferenceError: index is not defined
Stack trace:
@https://www.att.com/scripts/adobe/prod/detm-container-hdr.js:8:63513
  
detm-container-hdr.js:8:63732
XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:  
controllerdata:1:1
httpclient: 14:25:27.572: Warning -> post was successful but did not return anything  
ssaf-uc.js:2:3310
XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:  
controllerdata:1:1
httpclient: 14:25:27.684: Warning -> post was successful but did not return anything  
ssaf-uc.js:2:3310
ReferenceError: event is not defined[Learn More]  
enter_code.js:181:13
httpclient: 14:25:33.760: Warning -> SSAF UC MISSING IDSE_STACK MISSING  
ssaf-uc.js:2:3310
XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:  
controllerdata:1:1
httpclient: 14:25:33.864: Warning -> post was successful but did not return anything  
ssaf-uc.js:2:3310
ReferenceError: event is not defined[Learn More]  
enter_code.js:181:13
httpclient: 14:25:35.346: Warning -> SSAF UC MISSING IDSE_STACK MISSING  
ssaf-uc.js:2:3310
XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:  
controllerdata:1:1
httpclient: 14:25:35.454: Warning -> post was successful but did not return anything
Error Console

Code: Select all

Timestamp: 3/24/2023 2:14:16 PM
Error: DEPRECATION WARNING: This path to Console.jsm is deprecated.  Please use Cu.import("resource://gre/modules/Console.jsm") to load this module.
You may find more details about this deprecation at: https://bugzil.la/912121
Callstack:
resource://gre/modules/devtools/Console.jsm 19 null
chrome://downloads_window/content/modules/watchwindows.jsm 47 null
resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///C:/Users/Peter_S/AppData/Roaming/Moonchild%20Productions/Pale%20Moon/Profiles/0qxjtpdk.default/extensions/%7Ba7213cf2-fa1e-4373-88ff-255d0abd3020%7D.xpi!/bootstrap.js 144 startup
resource://gre/modules/addons/XPIProvider.jsm 4402 XPI_callBootstrapMethod
resource://gre/modules/addons/XPIProvider.jsm 2127 XPI_startup
resource://gre/modules/AddonManager.jsm 193 callProvider
resource://gre/modules/AddonManager.jsm 725 _startProvider
resource://gre/modules/AddonManager.jsm 861 startup
resource://gre/modules/AddonManager.jsm 2433 startup
jar:file:///C:/Program%20Files%20(x86)/Pale%20Moon/palemoon.res!/components/addonManager.js 58 observe

Source File: resource://gre/modules/Deprecated.jsm
Line: 85
Timestamp: 3/24/2023 2:18:48 PM
Warning: Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox”
Source File: chrome://browser/content/browser.xul
Line: 0
Timestamp: 3/24/2023 2:21:47 PM
Warning: Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
Timestamp: 3/24/2023 2:21:54 PM
Warning: A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element.
Source File: https://signin-static-js.att.com/scripts/att_common.js
Line: 1
Timestamp: 3/24/2023 2:21:59 PM
Warning: A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element.
Source File: https://signin.att.com/static/siam/en/otp/static/scripts/libs/jquery/3.6.0/jquery-3.6.0.slim.min.js
Line: 2
Timestamp: 3/24/2023 2:24:56 PM
Warning: Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive.
Timestamp: 3/24/2023 2:25:20 PM
Warning: A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element.
Source File: https://signin-static-js.att.com/scripts/att_common.js
Line: 1
Timestamp: 3/24/2023 2:25:23 PM
Warning: A form was submitted in the windows-1252 encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element.
Source File: https://signin.att.com/static/siam/en/otp/static/scripts/libs/jquery/3.6.0/jquery-3.6.0.slim.min.js
Line: 2
Timestamp: 3/24/2023 2:25:27 PM
Error: XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:
Source File: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line: 1
Timestamp: 3/24/2023 2:25:27 PM
Error: XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:
Source File: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line: 1
Timestamp: 3/24/2023 2:25:33 PM
Error: ReferenceError: event is not defined
Source File: https://signin.att.com/static/siam/en/otp/static/scripts/enter_code.js?v=17.2.1
Line: 181
Timestamp: 3/24/2023 2:25:33 PM
Error: XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:
Source File: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line: 1
Timestamp: 3/24/2023 2:25:35 PM
Error: ReferenceError: event is not defined
Source File: https://signin.att.com/static/siam/en/otp/static/scripts/enter_code.js?v=17.2.1
Line: 181
Timestamp: 3/24/2023 2:25:35 PM
Error: XML Parsing Error: no root element found
Location: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line Number 1, Column 1:
Source File: https://www.att.com/ssaf/ssafc/v1/controllerdata
Line: 1
Top
User avatar
Sajadi
Board Warrior
Board Warrior
Posts: 1228
Joined: 2013-04-19, 00:46

Re: Cannot Login to AT&T Email

Unread post by Sajadi » 2023-03-24, 19:31

ReferenceError: event is not defined

Could be that this is causing this, there is no workaround for this, you have to use a different browser for this page sadly.
Top
User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 36453
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:
Contact Moonchild

Re: Cannot Login to AT&T Email

Unread post by Moonchild » 2023-03-24, 21:22

You could also write to AT&T and/or Yahoo and (kindly) ask them to not use an ambiguous, globally-defined window event that is officially deprecated and not guaranteed to be present in browsers, and instead use the event as passed into the event handler (as one should).
"A programmer is someone who solves a problem you didn't know you had, in a way you don't understand." -- unknown
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Top
pshipwrite
Apollo supporter
Apollo supporter
Posts: 39
Joined: 2018-04-18, 21:34

Re: Cannot Login to AT&T Email

Unread post by pshipwrite » 2023-03-25, 21:31

Thanks Sajadi and Moonchild, for confirming the
ReferenceError: event is not defined
is the cause of the issue and, unfortunately, there is no Pale Moon workaround. I will use a chrome browser to access this email account.

I should add that AT&T implemented two factor authentication for all email users sometime in mid-March and they are getting some negative feedback. I suggested AT&T should have made TFA an opt-in choice, not mandatory. AT&T email is the only email provider I have which mandates TFA.
Top
Locked

Return to “Web Compatibility Support”