Issue 136197 in chromium: Can't login to Charles Schwab brokerage website with dev channel build

66 views
Skip to first unread message

chro...@googlecode.com

unread,
Jul 6, 2012, 5:01:29 PM7/6/12
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined OS-Windows

New issue 136197 by cbiesin...@gmail.com: Can't login to Charles Schwab
brokerage website with dev channel build
http://code.google.com/p/chromium/issues/detail?id=136197

Chrome Version : 21.0.1180.15
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) : http://www.schwab.com/getstarted
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: works (tested Windows Safari)
Firefox 4.x: works (tested Firefox nightly)
IE 7/8/9: works (tested IE 8)

What steps will reproduce the problem?
1. Go to the URL I mentioned above

What is the expected result?
Get a login form

What happens instead?
Get a "Functionality temporarily unavailable." error message

Please provide any additional information below. Attach a screenshot if
possible.

See the attached screenshot. The Schwab homepage (http://www.schwab.com)
works, but logging in from that page also shows the error. All other
browsers work.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.1
(KHTML, like Gecko) Chrome/21.0.1180.15 Safari/537.1



Attachments:
schwab.png 69.5 KB

chro...@googlecode.com

unread,
Jul 10, 2012, 11:52:07 PM7/10/12
to chromi...@chromium.org

Comment #1 on issue 136197 by sz...@chromium.org: Can't login to Charles
Schwab brokerage website with dev channel build
http://code.google.com/p/chromium/issues/detail?id=136197

Could not reproduce on Linux Chromium 20.0. Does the problem persist?

chro...@googlecode.com

unread,
Jul 11, 2012, 12:06:10 AM7/11/12
to chromi...@chromium.org

Comment #2 on issue 136197 by cbiesin...@gmail.com: Can't login to Charles
Schwab brokerage website with dev channel build
http://code.google.com/p/chromium/issues/detail?id=136197

Hmm, looks like this did get fixed. How do I close this issue?

Reply all
Reply to author
Forward
0 new messages