Sorry to confuse you, Jeroen.

I was pointing out the inherent difference between a Web form (HTML)
and a JavaScript alert or dialog handled at the OS or application
level (GUI). Gabriel's followup clearly refers to the HTML variety,
where the HTML source controls the button order on a form.

--Jim

On Dec 18, 1:52 pm, Gabriel Sean Farrell <[EMAIL PROTECTED]> wrote:
> On Dec 18, 1:35 am, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]
>
>
>
> nomine.org> wrote:
> > -On [20071217 23:20], fmi.jcrissman ([EMAIL PROTECTED]) wrote:
>
> > >I agree with your preference to place Save/Apply/OK before Cancel;
> > >however, on Linux, UNIX and MacOS, this button order is naturally
> > >reversed from Windows and similar GUIs. Trac, WebAdmin and the Web
> > >browser have no control in this context unless the buttons are
> > >strictly contained within a Web form.
>
> > How do you mean have no control? For all I know the order in which place the
> > buttons in your HTML define the order in which they get shown, no?
>
> > Looking at, say, the component modification screen within Opera 9.5 on 
> > Windows
> > XP the order is: Cancel/Save. This is indeed different from the expected
> > order. One could argue that it breaks the principle of least astonishment 
> > for
> > web forms given the majority is used to forms where save/ok and such are 
> > left
> > and cancel is right.
>
> The buttons are a part of the form, but I don't know what's meant by
> "strictly contained within".  And like my parent post, I'm confused by
> the assertion that we can't control the order.  The change I'm
> suggesting would be a small patch on the following files in trunk/trac/
> admin/templates: admin_components.html, admin_enums.html,
> admin_milestones.html, and admin_versions.html.  For each, the
> relevant snippet of the patch would look like so:
>
>            <div class="buttons">
> +            <input type="submit" name="save" value="Save" />
>              <input type="submit" name="cancel" value="Cancel" />
> -            <input type="submit" name="save" value="Save" />
>            </div>
>
> So yeah, not a big change.  Just checking for some reasoning behind
> the current behavior.  Seeing none, I'll go ahead and submit a ticket.
>
> Gabriel

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to