Bug 103250 - [testcase] Form autocompletion doesn't work if the form contains a textarea
Summary: [testcase] Form autocompletion doesn't work if the form contains a textarea
Status: CONFIRMED
Alias: None
Product: konqueror
Classification: Applications
Component: khtml forms (show other bugs)
Version: 4.5.4
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-05 00:39 UTC by Dima Ryazanov
Modified: 2021-03-21 00:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
testcase (402 bytes, text/html)
2008-04-20 02:59 UTC, George Goldberg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dima Ryazanov 2005-04-05 00:39:51 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
OS:                Linux

If a form contains a <textarea>, the data is not stored into the wallet. E.g.,

  <form action="..." method="post">
   <p>Name: <input type="text" name="name"></p>
   <p><textarea /></p>
   <p><input type="submit" value="Submit"></p>
  </form>

Of course, saving the contents of the textarea might not be a good idea, but the rest of the data should still be stored in the wallet.

An example of a stupid login page with a form that has a (readonly) textarea: https://efiling.uscis.dhs.gov/efile/
Comment 1 J Appel 2006-09-13 13:09:17 UTC
the wallet does not ask if the pass should be stored, confirming.
Comment 2 George Goldberg 2008-04-20 02:59:52 UTC
Created attachment 24421 [details]
testcase

Test case attached (also available at
http://www.grundleborg.com/kde/bugsquad/testcases/103250 )

Bug still reproducible in svn trunk r795406.
Comment 3 Samuel Brack 2011-01-05 00:33:46 UTC
Confirmed in 4.5.4, updating version.
Comment 4 Justin Zobel 2021-03-21 00:26:05 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 10 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.