Thread:Pecoes/@comment-3562424-20120422041911/@comment-3508190-20120425144937

I think the dialog should be as unbotrusive as possible. It should not get in the way. That's why I made it so small. I hope it's not so small that people keep clicking the wrong buttons, but there's only one way to find that out, isn't there? I kind of had the crazy thought, that it might be fun to have mulitple layouts for the dialog. You know the regular one - for that I would suggest this version - and maybe also a more horizontal and a more vertical one... At any rate there's room next to the i button for more buttons... If you think you can make a better layout, go for it. I'm more than anything concerned with the dialog's functionality. When you tab through the dialog the currently focussed input should be highlighted. When you enter text into the find-input the message inside needs to go away, but should re-appear when the input is blanked. The previous- and next-buttons should be disabeld as long as there's no content in the find input. When you click on the regex checkbox, the case-sensitive checkbox is swapped with the i-modifier and the m-modifier checkboxes. Etc. etc.

But speaking of regular expressions: I'm strongly against making them the default. Most people have no idea what regular expressions are and of those who do, many think of them as some sort of arcane art. That's why regular expressions should be optional. You're right of course: For the most common searches there's no difference between the regular and the regex variety. If you do a regular search for the word "test" it is internally translated into the regex /test/g anyway... But what if someone wants to search+replace inside a wikitable? The | character has special meaning in regexes. People who know that are welcome to click the regex checkbox, but the rest of the world should not be bothered with such intricacies.

EDIT:

I'll upload the latest dialog design some time later today - probably not to wikia as my test page is a regular web page. And I'll look at your code of course!