Implemented comprehensive form element access, manipulation, and submission control:
• Extended DOM system to create form elements during HTML parsing (INPUT, TEXTAREA, SELECT)
• Added JavaScript form properties: name, action, method, elements array access
• Implemented form.submit() and form.reset() methods with w3m form system integration
• Fixed DOM element creation timing issues for reliable getElementById functionality
• Added early JavaScript initialization during HTML parsing to ensure DOM availability
• Enhanced form submission control connecting JS API to w3m's _followForm mechanism
• Updated keybindings documentation with navigation commands (d, e, f, p)
• Added console.log JavaScript API for debugging support
All Phase 4 objectives completed and tested - form JavaScript integration fully functional.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Translating Documentation
* Create README.SSL from doc-jp
* Clarified wording on some functions
* Clarified English in README.img
* Created README.keymap
* Translated README.menu
* Minor grammar changes
By default, w3m puts all of its data in the `~/.w3m/` directory
(creating it as necessary). This was not configurable in any way.
This commit adds some quick reconfigurability -- when the "W3M_DIR"
environment variable is set, w3m will use that location instead. The
default location is unchanged.
Fixes#130.
- Begin a sentence on a new line.
- Split long lines (> 80).
- Fix warnings from "mandoc -Tlint"
- Remove space at end of lines.
- Change a HYPHEN-MINUS (code 0x55, 2D) to a dash (minus) if it matches
" -[:alpha:]" or \[aq]-[:alpha:] (for options).
- Use the macros .MT/.ME for e-mail addresses
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963801#5
Since Google gives usable search results to Lynx but not to w3m, and
many other sites block Lynx but /not/ w3m, we want to be able to set
the User Agent string on a per-site basis.
