doron's blaahg

to be installed on every client's machine ;-)

seriously, the main reasons i use mozilla for my web development are the extra tools (thus the UI, which you didn't want comments about).

fully supported rich text editing support? (i know midas exists; how reliable or otherwise is it?)

native database connectivity - i'd love to be able to develop apps in XUL and have them connect to a remote data source (ODBC/JDBC).

A calc program would not be a bad idea, Google and AllTheWeb implemented calcs, calcs are really good if i can stick it with a keystroke, for making calcs while i'm coding.

Also a better composer would be good, i think composer should be like an ultraedit program, not as a frontpage, because sometime it looks like Frontpage (i don't want to offend).

Ben's initial joke comment does rather hit the nail on the head - the website I maintain has about 5% hits from Gecko. So there's not much Gecko can do for the audience as a whole.

100% compatibility with IE would save on a little testing ;) Aside from that, what's needed is the people looking at the site to have Gecko...

How about highlighting the access key in HTML elements (bug 56701) or support for the CSS3 "nth" selectors (bug 75375)? I know this is really a UI issue, but I'd really like alternate stylesheet selection to be remembered between pages (bug 83663).

Yeah, market share would be so good. Though it's mostly up to us to get it. *has only converted three people so far this month - not good*

As was also already said, most of what makes Mozilla good for webdevelopers is in the UI. view selection source. The javascript console. And of course the DOM-Inspector, without which I do not think life would be worth living... :)

:contains() and some parts of css3 text would be nice though. There will come a time when complete superiority of which parts of the standards are usable with gecko will make the difference wrt webdesigners just not bothering with IE anymore. Once that happens enough the remaining people using it might finally switch to decent browsers.

I'd love to see:
* The ability to open the source in my editor of choice.
* Midas being configurable to use plain HTML tags instead of s
* Nice market share like said above.

Really old nagging layout bugs fixed.

There are a few out there that I seem to hit semi-regularly that I'd love to see fixed. Unfortunately they're probably all so time consuming to fix that its easier to wait for some great overhaul to fix 'em. I think I hit them mostly working with floats where I see stuff like bug 50630.

I'd also love to see good/working/finished support for outline so I can rewrite my bookmarklets and toolbar to use that instead of borders so I run into less of a chance of clobbering layout/designs.

Gecko should seperate words connected with "-". Not doing this often destroys the layout of a site.

As mentioned several times already:

* Some parts of CSS 3 need to get implemented
* Fix remaining CSS 1+2 issues (like a abs. positioned div in a table bug)
* DOM perf. needs attention
* Remove -moz extensions in CSS implementation (ex. -moz-opacity)

mini-d: Calc is easy: Create a bookmark with the content

javascript:with(Math){ %s }

Give it a keyword, e.g. calc.

Then enter into the URL-Bar:

calc 2+pow(sin(PI/2),2)

Voilá!
(BTW: It's even easier to start bc from the command line).

I'd like to see more of CSS2/3 and SVG.

Oh, one more thing... downloadable fonts. Nav 4 used to be able to do it, but it was crappy. IE can do it (If I remember correctly).

i'd like to see a quick-and-easy tutorial on implementing midas, and the ability to integrate it with sematically meaningful XHTML. (e.g. have buttons for cite, em, & strong)

To put my money where my mouth is, in each new article I'll build a hypothetical application that illustrates the guidelines I'm covering. Today's application is called "Paint" and will be based on the photo-illustrative icon I created in my last article. Together we will complete each step, and by the end of the project we should have a well-designed, 95%-100% Aqua-compliant application. I'll leave some room for personal preferences and the fact that Apple changes the OS every few months.

By building an application that takes advantage of Aqua's many facets, you help ensure that your application will not only look good, but have a chance of becoming a raging success. After a new user clicks on the icon of your program, the first thing he or she sees is the application interface. I know that when I review a product, I am very critical of its visual design. I usually have a short time to learn the new software, so design and ease of use are very important. Aside from those who marvel at the beauty of the command line, most users tend to react the same way.

Adhere to System Appearance. Does your application use all the sweetly colored buttons, delightfully shaded windows, and all the other "bells and whistles?"

Adopt Sheets. I really like the use of Sheets in OS X. The use of Sheets lets me know which window my dialogue belongs to without hijacking my system.

Clicking an application in the dock should always bring forward an active window. If the user clicks on an open app's icon in the Dock, the application is active and all unminimized windows come along with it. I have found a few problems with windows behaving independently of their application.

To put my money where my mouth is, in each new article I'll build a hypothetical application that illustrates the guidelines I'm covering. Today's application is called "Paint" and will be based on the photo-illustrative icon I created in my last article. Together we will complete each step, and by the end of the project we should have a well-designed, 95%-100% Aqua-compliant application. I'll leave some room for personal preferences and the fact that Apple changes the OS every few months.

You Must Promise. To call your mother, to help old ladies cross the road, and to turn your cell phone off at the movies.

Adhere to Layout Guidelines. Did you leave 12 pixels between your push buttons? Does the positioning of your pop-up menus make sense, and when do you use a pop-up versus a scrolling list? Are you using the right types of buttons for the proper functions?

If an application is designed well, the reward for users is that they will learn it faster, accomplish their daily tasks more easily, and have fewer questions for the help desk. As a developer of a well-designed application, your returns on that investment are more upgrade revenue, reduced tech support, better reviews, less documentation, and higher customer satisfaction. The rewards of building a good-looking Aqua application are worth taking the extra time.

Adopt Sheets. I really like the use of Sheets in OS X. The use of Sheets lets me know which window my dialogue belongs to without hijacking my system.