Bug 116799

Summary: [site-issue] incompatible with http://www.meebo.com/ JS web messenger
Product: [Applications] konqueror Reporter: patcito <patcito>
Component: khtmlAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: finex, lex.lists
Priority: NOR    
Version: 3.5   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description patcito 2005-11-21 01:13:23 UTC 
Version:           3.5 (using KDE 3.5 (RC1), Kubuntu Package 4:3.5-rc1-0ubuntu0breezy1 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12-9-386

http://www13.meebo.com/ is a website that offers a free (as in beer) web messenger that connects to yahoo/aim/msn/jabber.

When I try to connect to log in I get:
"Meebo does not support your browser yet.  Stay tuned!"

I tried to change browser identification to both IE and Mozilla but it didn't work out.

Could please check what the problem is? :)

Thanx in advance.
Comment 1 lexual 2006-11-02 23:49:42 UTC 
Site doesn't work with konq 3.5.5 with any UA.
Site works with firefox 1.5
Comment 2 Becheru Petru-Ioan 2007-10-16 17:35:43 UTC 
Now(konqueror 3.5.8) works to view the webpage, but after writing user/pass, the loading is stopped showing "Signing on. Please wait..."(the browser encrypts the passwords).
Comment 3 radu 2008-04-25 15:48:39 UTC 
konqueror 4.0.3 release 18.2: the site shows and works with a bug - when you create a new account and then chose the chat system of your choice, the text cursor will not show up in the username and password textboxes upon mouse clicks. it works with <tab> and iintuition because you dont see any trace of the cursor until you start typing. after that everything was smooth. I did not chat though because i do not have any chat accounts in those services. but the loca chat looked ok
Comment 4 FiNeX 2010-08-15 22:41:13 UTC 
The reported bug is not reproducible. Anyway the webiste doesn't works well with Konqui/KHTML, but it looks a different bug so I'm closing this.