Revision history [back]
 | 1 | initial version | posted 2015-01-14 17:31:23 +0200  |
Can the native browser become user-configurable to treat plaintext file content as if it were wrapped in PRE CONTENTEDITABLE TRUE-attributed HTML?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save local files via browser),
| | 2 | No.2 Revision |
Can the native browser become user-configurable to treat plaintext file content as if it were wrapped in PRE CONTENTEDITABLE TRUE-attributed HTML?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save contebnt to local files via the native browser), 73458.
| | 3 | No.3 Revision |
Can the native browser become user-configurable to treat plaintext file content as if it were wrapped in PRE CONTENTEDITABLE TRUE-attributed HTML?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save contebnt content to local files via the native browser), 73458.
| | 4 | No.4 Revision |
Can the native browser become user-configurable to treat plaintext file content as if it were wrapped in PRE CONTENTEDITABLE TRUE-attributed HTML?a pre or p tag with the contenteditable attribute set to True?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save content to local files via the native browser), 73458.
| | 5 | retagged |
Can the native browser become user-configurable to treat plaintext file content as if it were wrapped in a pre or p tag with the contenteditable attribute set to True?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save content to local files via the native browser), 73458.
| | 6 | No.6 Revision |
Can the native browser become user-configurable to treat plaintext file content as if it were wrapped in a pre or p body (or any) tag with the contenteditable attribute set to True?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save content to local files via the native browser), 73458.
| | 7 | No.7 Revision |
Can the native browser become user-configurable to treat plaintext file content as if it were a body (or any) tag with the contenteditable attribute set to True?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save content to local files via the native browser), 73458.
This will bring the benefit of having a text editor within a very few taps. It would be important in the implementation to not lose unsaved edits just by changing tabs.
| | 8 | No.8 Revision |
Can the native browser become go user-configurable to treat plaintext file content as if it were a body (or any) tag with the contenteditable attribute set to True?attr[contenteditable="True"]?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save content to local files via the native browser), 73458.
This will bring the benefit of having a text editor within a very few taps. It would be important in the implementation to not lose unsaved edits just by changing tabs.
Can the browser go user-configurable to treat plaintext as with attr[contenteditable="True"]?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save content to local files via the native browser), 73458.
This will bring the benefit of having a text editor within a very few taps. It would be important in the implementation to not lose unsaved edits just by changing tabs.
| | 10 | No.10 Revision |
Can the browser go user-configurable to treat plaintext mimetype text/plain as with attr[contenteditable="True"]?
With this plaintext parser behaviour as default, local text files (given the relevant read/write permissions) become more accessible and useful.
This request depends upon another requested feature (save content to local files via the native browser), 73458.
This will bring the benefit of having a text editor within a very few taps. It would be important in the implementation to not lose unsaved edits just by changing tabs.