aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn
diff options
context:
space:
mode:
authorhttp://lj.rossia.org/users/imz/ <http://lj.rossia.org/users/imz/@web>2011-01-12 04:20:35 +0000
committerJoey Hess <joey@kitenet.net>2011-01-12 04:20:35 +0000
commit32ffffcf2a71b896007253891be5bc6f12e763ea (patch)
tree9ed32b8f3070c289f0d76a8d8653a4e1a063686e /doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn
parent1351913862ecd49cea391bb5c8acff52f4b7e83d (diff)
downloadikiwiki-32ffffcf2a71b896007253891be5bc6f12e763ea.tar
ikiwiki-32ffffcf2a71b896007253891be5bc6f12e763ea.tar.gz
perhaps not a problem of ikiwiki, if it's correct pure HTML
Diffstat (limited to 'doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn')
-rw-r--r--doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn b/doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn
index 99b274987..46bca15c7 100644
--- a/doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn
+++ b/doc/bugs/no_search_button__44___hence_can__39__t_do_search_in_w3m_at_ikiwiki.info.mdwn
@@ -8,3 +8,19 @@ In the more "complete"
browsers (Chromium etc.), the request is done by pressing Enter in the
text field.)
--imz
+
+I see, no Javascript is probably involved in using the search form;
+the code is simply:
+
+ <form method="get" action="/ikiwiki.cgi" id="searchform">
+ <div>
+ <input type="text" id="searchbox" name="P" value="" size="16"
+ />
+ </div>
+ </form>
+
+So, if the semantics suggested by HTML is such that such a form is to
+be submitted by some default form submitting action in the UI and it
+doesn't really require a button to be functional, then I'd say it's
+not an ikiwiki's problem, but a missing feature in the UI of emacs-w3m
+or the underlying w3m... Perhaps I'll report this issue to them. --imz