Opened 14 years ago
Closed 11 years ago
#6473 closed bug (fixed)
Google mail problems
Reported by: | 2ck | Owned by: | stippi |
---|---|---|---|
Priority: | blocker | Milestone: | R1 |
Component: | Applications/WebPositive | Version: | R1/alpha2 |
Keywords: | r488 | Cc: | |
Blocked By: | Blocking: | #7823, #8813, #8968, #9146 | |
Platform: | All |
Description
Google mail doesn't function properly with, at least, this version of web positive. An error occurs when sending mail through the standard interface with a prompt to retry, and a general error notification appears at the top of the window designated '#500'. The HTML interface seems to work fine.
Change History (12)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
This is a known issue that's most likely due to problems with AJAX handling. It's possibly a bug in the libcurl backend that Web+'s WebKit implementation is currently using, and may be fixed when it's switched over to using the services kit (though that will have to wait partly until services kit has https support, since that's required for gmail authentication).
comment:3 by , 14 years ago
Until this is fixed, GMail is still usable when viewed in "Simple HTML" mode.
comment:5 by , 13 years ago
Using build 583 of W+ and Haiku build 42714, I can't bring up the Google Mail web page at all. It will bring up other Google pages but not that one. It doesn't even start to load the page as far as I can see. Just sits there with a partial progress bar that never moves.
comment:6 by , 13 years ago
With build 586 of W+ and Haiku build 44016, there's a big improvement. Everything seems to work well EXCEPT for when you hit send on an e-mail message. Then it returns the following message in a little window:
"Your action was unsuccessful. Please try again."
comment:8 by , 12 years ago
Priority: | normal → blocker |
---|
comment:9 by , 12 years ago
Blocking: | 8968 added |
---|
comment:11 by , 11 years ago
With the new WebKit, this seems to work fine for me (albeit with a ton of rendering problems). Functionality seems correct, though.
comment:12 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The error indicates a browser problem but has no specific, stated cause.