Firefox/Feature Brainstorming:Form handling and text areas: Difference between revisions

{{FeatureBrainstorming}}

== Web Forms 2.0 implementation ==

* Allow using of the extended forms. See the standard made by whatwg, which is located at [http://www.whatwg.org/specs/web-forms/current-work]

Enhanced the TEXTAREA tag to provide a WYSIWYG editor that generates HTML code.  How many different Javascript, ActiveX, Applet and AJAX solutions exist for this problem?  How many of them <u>actually work</u>?  None.  Let's fix this problem once and do it right.  Imagine:

The user would see a text box with WYSIWYG editing controls.  When the form submits, the field would contain HTML code for the user's content.  Other browsers would ignore the new flag and display a standard TEXTAREA.

<u>EVERYONE</u> needs this, including this Wiki.

:However we would be breaking the standards, wouldn't we? And i think we shouldn't be trying to do W3C's job.

== Use mouse wheel to modify the values ==

or

* provide a separate page or a tab in Page info where the contents of forms that are sent last are shown.

== Autofill forms ==

* Like Internet Explorer - it is best way.

* With Firefox 2, login form fields are only filled in with the login information stored in password manager after loading of the entire page has completed. However, form fields (in particular for login) should be rendered before any other elements on a page, because often all you want to do on a login page is ... to log in. But instead, rendering of a login page often hangs because billions of annoying ad servers take forever to reply to client requests. Rendering (login) forms and filling in the login information first would allow for immediate login, without having to wait until rendering of the whole page is complete -- also contributing to save bandwith, as requests to the billions of annoying ad servers would not be send, or at least cancelled immediately.

== User-created spell check blacklist ==

* Allow users to submit form buttons to a new tab/window

== Change the way the spell checker highlights the misspelled words ==

User interface consistency is important. I think misspelled words should be underlined with a red zigzag line, much like it's done on all modern text processors, instead of the current dotted line.

[added:stk 10-mar-07]

When I am reading a long article, paging down, it is annoying to reach the last page only to find that it is shorter than all the other pages and now my place is lost somewhere in the middle of the screen. I have to hunt for where I left off. I could solve this using the mouse to scroll, and sometimes I do, but I find that more burdensome than just hitting page down. This behavior has existed since the earliest days of the web. It seems to me the easiest way to fix it is for the browser to position the last line of the current page as the first line of the next, no matter what, and fill the rest of the window as needed with blank space. Since I spend most of my web time reading text, consistent text positioning would be a major usability enhancement for me.

== Drag and dropping files into textboxes ==

* The clipboard does not affect copy and paste in any way. It merely pastes all instances of copying into its memory. Pasting an item from the clipboard merely copies the item from the history and pastes it, as if the user did it manually.

* The order of the items on a clipboard can be sorted via up/down buttons.

== Allow specified textareas to expand with the size of the window ==

Actually, there is a great piece of software called Badboy[http://www.badboy.com.au/] which does something similar, it has a lot of excellent features. Unfortunately it is only available for a specific OS and becuase it is not portable I can't use it. I appreciate that web-app testing is probably beyond the scope of core Firefox but maybe a seperate component/plug that does this could be considered.

== Searchable button labels ==

Make button labels searchable, so that you can text search (for example) this page for "Search" and have the cursor on the "Search" button at the top.  This would help with navigation, especially in large webpages.  First, like text search in general, it allows the focus to be positioned directly without using a pointing device, which is often faster.  Second, there is often a specific button or function (such as search) which users want to use and have to scroll through the page and look for it manually. -[[User:Pgan002|Pgan002]] 15:07, 8 May 2007 (PDT)