10
edits
Changes
no edit summary
* Here is a [http://adesklets.sourceforge.net/verbatim/cairo/test.html simple page]; right now, it looks like [http://adesklets.sourceforge.net/verbatim/cairo/firefox_now.jpg this], and it would be nice if we could have it look like [http://adesklets.sourceforge.net/verbatim/cairo/firefox_wished.jpg that] instead.
== Adopt standard OS X keyboard navigation in & text fields behaviors ==
* While in a (single line) text field hitting the up arrow in all(?) other OS X apps, and the OS itself, will take the cursor/insertion point to the beginning of any existing text, likewise hitting down will move it to the end. The currently required use of the Cmd modifier key is proprietary to Firefox, and so not intuitive.
* Cmd-downarrow / Cmd-uparrow do work correctly in multi line form textareas but not in single line 'input type="text"' fields. Also this does not work in the web address / navigation bartoolbar when manually typing or editing a URL.* Triple clicks do not select the paragraph as they should, instead they select the 'line' of text (not a sentence). Triple click in Firefox on Mac OS X:[[Image:FF Triple Click.jpg]] Triple click in Mac OS X Apps:[[Image:Mac Triple Click.jpg]] * Double clicking & holding mouse down and dragging should select a word and add / subtract words from the selection (click down -> mouse up > mouse down and hold -> move mouse). White space and punctuation after a word should not be added to the selection with the preceding word; they should be treated as single characters.* CMD-E should be mapped to 'Use selection for Find' like native mac apps do. This allows you to double click a word (or double click and drag to select multiple words), 'CMD-E' then 'CMD-G' to find the next occurrence (without opening any GUI find panel, window, or search field).* XUL tab views do not use native mac looking tab-view's, checkbox cells, radio button cells, and others as well... (Reasonable people could debate how arrow keys should work, but the default behavior should perform like other Mac apps do, and they way mac users expect them to behave. Because the text system behaves differently I end up using Safari/Camino/OmniWeb most of the time and when I need to use FF, I only use it for a specific task because navigating on a page and between pages is feels so foreign. I have to re-teach my fingers and it makes me think about the browser instead of the task.)
