# HG changeset patch
# User paulb
# Date 1121704872 0
# Node ID 5bfdc16d4a915f032db39b8858d7517d97b12e7b
# Parent  746246e79bcb36b6bc3f6694f95f0b9cda87b5ab
[project @ 2005-07-18 16:41:12 by paulb]
Added various workarounds for Konqueror's not-totally-compliant DOM element
manipulation support where removed form fields still manage to have their
values submitted.

diff -r 746246e79bcb -r 5bfdc16d4a91 README.txt
--- a/README.txt	Sun Jul 17 22:38:10 2005 +0000
+++ b/README.txt	Mon Jul 18 16:41:12 2005 +0000
@@ -44,6 +44,15 @@
 Notes on In-Page Update Functionality
 -------------------------------------
 
+Special note: Konqueror seems to remember replaced form content (when
+replaceChild is used to replace regions of the page which include form
+elements). This causes the browser to believe that more form fields exist on
+the page than actually do so, and subsequent form submissions thus include the
+values of such removed fields. A special hack is in place to disable form
+fields by changing their names, thus causing Konqueror to not associate such
+fields with the real, active fields; this hack does not seem to cause problems
+for Mozilla.
+
 Various browsers (eg. Mozilla/Firefox, Konqueror) will not allow the
 XMLHttpRequest in-page updates to function unless the application URL defined
 within the Configurator application (and other relevant applications) matches