Bug 351228

Summary:	Dropbox for attachments configuration loads a web part that doesn't work
Product:	[Applications] kmail2	Reporter:	Eric Mesa <ericsbinaryworld>
Component:	config dialog	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	4.14.7
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description Eric Mesa 2015-08-12 18:55:29 UTC

While looking through the Kmail options today, I saw that for large attachments, Kmail can send the file to dropbox and generate the link. But when I try to authorize Dropbox to Kmail, the website that's loaded doesn't work. I can type in my username/password, but the website doesn't recognize that I've typed anything and so the button to authorize it never becomes ungreyed. 

If it helps solve what the problem is, the placeholder text that tells you what to type into the box remains superimposed over what I'm typing. In normal operation on websites, this text disappears when the user starts typing. 

Reproducible: Always

Steps to Reproduce:
1. Go to config for attachments
2. Try to configure dropbox
3. Type in username (I think it's email) and password
4. Try to click on the button to authorize it

Actual Results:  
Can't click button because it (apparently) doesn't know I'm typing

Expected Results:  
Should allow me to authorize dropbox.

Comment 1 Denis Kurz 2017-06-23 19:56:23 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 2 Denis Kurz 2018-01-31 16:52:51 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.