Should OK button be on left of Cancel button or vice versa?

Are there any studies suggesting either of the solutions?

  • 27
    It's not a duplicate; your question was about alignment, this is about positioning (close, but still different!)
    – Rahul
    Commented Aug 30, 2010 at 8:14
  • 10
    @ign - Also not a duplicate... similar, not duplicate. :)
    – Rahul
    Commented Sep 1, 2010 at 15:15
  • 6
    Just to add to the conversation, Luke Wroblewski also wrote an article called "Primary & Secondary Actions in Web Forms" where he shares the results of some eye tracking research. Commented Sep 1, 2010 at 21:13
  • 1
    Note, incidentally, that just trying to detect the user's OS doesn't necessarily help-- at least not if you detect the OS as being Linux. Because of the two most popular Linux desktops out there, KDE uses Windows button ordering, and GNOME desktop uses Mac button ordering.
    – calum_b
    Commented Sep 1, 2010 at 21:20

24 Answers 24


As with everything: user test! Thankfully, usability hero Jakob Nielsen jumps to the rescue here in his Alertbox article about OK/Cancel buttons:

Should the OK button come before or after the Cancel button? Following platform conventions are more important than sub-optimizing an individual dialog box.

Kostya was right on the mark in advising adherence to platform guidelines. But what about web-based platforms?

If you're designing a Web-based application, the decision is harder, but you should probably go with the platform preferred by most of your users. Your server logs will show you the percentage of Windows vs. Mac users for your specific website or intranet. Of course, Windows generally has many more users, so if you can't be bothered to check the logs, then the guideline that will apply to most situations is OK first, Cancel last.

He also mentions two additional important guidelines you might consider when creating OK/Cancel buttons:

  • It's often better to name a button to explain what it does than to use a generic label (like "OK"). An explicit label serves as "just-in-time help," giving users more confidence in selecting the correct action.
  • Make the most commonly selected button the default and highlight it (except if its action is particularly dangerous; in those cases, you want users to explicitly select the button rather than accidentally activating it by hitting Enter).
  • 28
    Luke Wroblewski also wrote a more in-depth article called "Primary and Secondary Actions in Web Forms" (lukew.com/resources/articles/psactions.asp) that includes the results of eye-tracking studies. Commented Sep 1, 2010 at 21:15
  • 7
    No offense Rahul, but I can't believe that this answer got that many upvotes. First of all it's not a matter of user tests but about AB testing if anything (which is not the same) Second of all The advice about looking at the server log to see whether you will most likely have mac or windows users is straight out bad advice.
    – ThomPete
    Commented Nov 14, 2010 at 20:16
  • 10
    @ThomPete Um, okay. If you're going to argue with Jakob Nielsen, can you provide some reasons other than "it's straight out bad advice"? It sounds like it makes a lot of sense to me: look at the data and make decisions from there instead of guessing. Yes, AB testing would work here too - but so would user testing, and IMO you learn a lot more from user testing than from AB testing, so I recommend that first. Finally, the reason this got a lot of upvotes is because Joel Spolsky tweeted it at some point and that probably blew things out of proportion a bit.
    – Rahul
    Commented Nov 15, 2010 at 7:36
  • 9
    With regards to the bad advice. It's bad because on the web people are not mac or windows users. They are browser users.
    – ThomPete
    Commented Nov 15, 2010 at 8:09
  • 4
    User testing variations of the design will tell you a lot, for instance whether you're dealing with users with a Mac background and therefore certain expectations on location of Cancel vs OK. Just because people are using the web platform doesn't mean they don't bring along expectations set by the software platform they're using, so Jakob's advice is good because it reminds you to think about that when designing for the web. It's not mutually exclusive - you can take platform into account while at the same time being aware of the fact that you're designing for the web.
    – Rahul
    Commented Nov 15, 2010 at 8:59

The answer is in user interface guidelines for the system you use.

For Windows

Present the commit buttons in the following order:

  • OK/[Do it]/Yes
  • [Don't do it]/No
  • Cancel
  • Apply (if present)
  • Help (if present)

So Cancel is always on the right of OK button.

For MacOS

A button that initiates an action is furthest to the right. The Cancel button is to the left of this button.

So for MacOS users Cancel is on the left of OK button.

For Android

The dismissive action of a dialog is always on the left. Dismissive actions return to the user to the previous state.

The affirmative actions are on the right. Affirmative actions continue progress toward the user goal that triggered the dialog.

For Android, Cancel is on the left of the OK button.

For other systems see guidelines.

  • 6
    Unfortunately there are no guidelines for the internets, so you'll have to use best practices there!
    – Rahul
    Commented Aug 30, 2010 at 8:15
  • 10
    @Kostya - This will cause problems when people view the same websites on different systems, there would be no consistency which is one thing you should expect from a good website.
    – Toby
    Commented Aug 30, 2010 at 12:33
  • 5
    @Toby But this is actually used, for instance, on this very website! I've worked with the source of the editor they use here, and it has this exact behavior, for the image and hyperlink dialog boxes - take note of it the next time you use it on different OS
    – Yi Jiang
    Commented Sep 8, 2010 at 14:37
  • 2
    @Toby: That would be an interesting follow-up question to this one: is it better for a website to adhere to a single behavior or change depending on the user's platform? Calum Benson also raises a good point about OS detection not being enough for Linux. Commented Nov 14, 2010 at 1:49
  • 2
    I've used both a Mac and a PC every working day for the last 10 years - and I hadn't actually realised the Yes/Save buttons were in a different order until I came across this question... So based on that sample of one observation, the order may not be that important.
    – PhillipW
    Commented May 17, 2011 at 19:17

Think "reading" metaphor. Westerners read left to right, our brains are conditioned to flow left to right. CANCEL is basically a step backwards (left) and OK/SUBMIT/YES/Etc., are a step forward (right).

  • 5
    Also timelines usually go from left to right. So Cancel would correspond to go back in time. And OK would be to move forward in time. Good analogy there.
    – neoneye
    Commented Aug 31, 2010 at 20:24
  • 14
    Specific platform conventions trump the broad reading direction argument. Windows does OK|Cancel.
    – dbkk
    Commented Sep 27, 2010 at 18:33
  • 22
    I agree with the reading metaphor, but you could just as easily come to the conclusion that since you read from left to right, top to bottom, that the buttons should go in order from most likely to least likely to do. In other words Ok, then Cancel. Ultimately however, I believe that following what your users expect is the most important and trumps anything else (i.e., platform conventions).
    – Nemi
    Commented Oct 27, 2010 at 17:56
  • 2
    @dbkk: in the case where you are serving a multi-platform userbase, then this would be a good "tie-breaker" argument. It may be better than detecting which OS the user is on and trying to conform to that (and as a result, show the same user different behavior depending on whether he's on his laptop or desktop or iphone). Commented Nov 14, 2010 at 1:45
  • 1
    I think that the most commonly used operations should be first and the least last. Submit/Cancel are not like Prev/Next in the manner that Prev/Next are undo-able (by clicking on Next/Prev) and Submit/Cancel are not. Commented May 2, 2012 at 18:45

It seems like Windows OK/ Cancel convention has done a lot of brain conditioning for users. So usability tests would certainly come out with lots of people looking for an OK button on the left, Cancel on the right.

But that doesn't change the most basic instinct of someone who is interacting with the system without any pre-conditioning. My basic instinct says that the OK/ Approval/ Move Forward button, no matter what colour or size you apply to it, needs to be on the right edge of the dialogue box.

Consider this dialogue box, with no labels or colour highlights:

enter image description here

Where would you click? I'd click on the button on the right edge, if I am looking to submit the form. The reason is, that before Windows, I've been conditioned into my instinct in the following ways:

  • The English language flows left to right.
  • The browser navigation works Back(left) and Forward(Right). enter image description here
  • Old 2D games like Dangerous Dave move the character to the right, when they are progressing further.

enter image description here

  • Numbers on the number line increase to the right, decrease to the left.

  • Atomic weights on the periodic table increase to the right.

  • The clock ticks to the right.

  • Calendar increases dates to the right.

I think the Windows platform has created an anti-pattern with OK/Cancel, that is now so widespread that its validating usability studies. But if you consider the factors above, I believe keeping the primary button on the right is justified and a defensible position.

EDIT: One additional factor to consider is consistency. If you expect additional buttons in your dialogue boxes, the primary button on the right edge would help to stay consistent with placement. A visual example would make this clear:

enter image description here

  • 4
    Best answer for me!
    – daniel
    Commented Sep 26, 2014 at 10:25
  • 4
    But the original poster is not asking about Next and Back buttons, he is asking about OK and Cancel buttons. OK doesn't necessarily mean a flow to the right, it just means a positive action. Actually if your argument is about flow of document, then for a web document your Next button should go underneath your Back button. Commented May 7, 2015 at 11:19
  • 7
    @SethJeffery OK is proxy to progression in a dialogue.
    – Adnan Khan
    Commented May 8, 2015 at 2:13
  • This is absolutely what i thought too. I also agree above answers to place OK first (thats left) but only when the button-group is aligned left or center. In mobile's world, i like to align button group right, for better touching with the right hand thumb. And in that case, i would also place the "main" button in the right corner.
    – Ruwen
    Commented Jan 10, 2017 at 10:27
  • 1
    In the dialog without labels example I would argue that left-right thinking might not apply, even if user is preconditioned by having i.e. turned book pages. If there is a choice to be made by clicking on a dialog button, when thinking left to right, 1st choice can be assumed as the correct one (positive action) while asecond choice is the negative action.
    – too
    Commented Mar 13, 2019 at 14:07

IMHO it does not matter too much where you will place "OK" button: to left or to right. It does not matter what kind of users visit your site (with hebrew or arabic languages). It does not matter what kind of software they use. The stats tell us that 55% of users want to see "OK" button from the right but if we will put it to the right, then the other 45% of users will be dissatisfied.

The best solution is to emphasize "OK" button (make it more prominent than "Cancel") and all the users will indicate "OK" button easily as more important and primary button.

Google and other companies use this approach in their software.

enter image description here

  • 3
    I agree that the visual weight and labels of action buttons are an important design aspect to consider (and very useful in this case where position alone can't be relied on), but it’s not the only aspect. I feel that a meticulous designer would think about how every design aspect affects the user - position cannot be ignored.
    – M.A.X
    Commented Dec 5, 2012 at 19:20
  • 1
    Actually I think the example you're using is more about organizational continuity (supported by this article mentioned in other comments) in that users are already scanning/interacting vertically down the left side, so the primary action should be on the left to remain consistent.
    – drzaus
    Commented Nov 23, 2016 at 16:04

For users whose language is read left to right, I would suggest putting the OK button to the left, since those users would ascribe greater importance to the first thing they see.

This would allow this subset of users to complete their task as quickly as possible.

  • 2
    Interesting mention of LTR, because it implies you would have to think differently about RTL. Surely there is some research done in that area?
    – Rahul
    Commented Aug 30, 2010 at 8:16
  • 1
    @Rahul: That might be a good reason to arrange them vertically if you can. I don't know of any languages where you read from the bottom up, and pretty much all interfaces with vertically arranged buttons put the affirmative at the top, so it would be both culture and platform agnostic. Commented Nov 14, 2010 at 1:47
  • 2
    I don't know about research, but Microsoft put a lot of effort into reversing UI elements like this for RTL.
    – ICR
    Commented Jul 6, 2011 at 12:06
  • 2
    @Graham When I am use English UIs, I read buttons or links from left to right until I find the one I am looking for. I don't see how you can read multiple buttons simultaneously, are you a Homo-Sapian? Commented May 2, 2012 at 18:49
  • You read from left to right, but you generally continue scanning until you've read all of them (especially when there are few buttons (2 or 3). So you would either read: "Ok, Cancel, Ok" (once you've reached the end you come back to the one you want) or "Cancel; Ok": great! No need to go back with this one. :) Commented Jun 13, 2017 at 10:12

Luke Wroblewski wrote a book about web forms (Web Form Design: Filling in the Blanks) and he also covered some principles like: "Primary & Secondary Actions" ( https://www.lukew.com/ff/entry.asp?571 ), "Top, Right or Left Aligned Form Labels" ( http:// www.lukew.com/ff/entry.asp?504 ) or "path to completion", etc. (you can read also http://www.uxmatters.com/mt/archives/2006/07/label-placement-in-forms.php)

So, IMO depending on what label placement you have (preferable vertically) and left-to-right + top-down rules, in order to have a good path to completion you should place primary action first (OK) and then secondary ones (++Cancel)

EDIT: Label placement in forms, by Caroline Jarrett, 2010 http://www.formsthatwork.com/files/Articles/labels-on-forms-for-uxlx-2010.pdf


I think everyone had given good point but there is one more key point to be mention here.

Buttons such as Ok/Submit/Save etc are called positive action buttons. Similarly, buttons such as Cancel/Reset etc are called negative action buttons.

Now to answer the query, most of them has come with some good points but here is another perception that is User Testing of an application usually decide most of the issues. After all any application created are for users only.

There were some eye moment test & heat test were done on users and still being done depending on the labs availability. The best scenario comes up are that most of users start looking at the web application or any other application from Left - to - Right & from top corner and start scrolling toward the bottom picking up key hotspots and generally end toward the left bottom thus it is always good to keep positive action button on left and negative action buttons on right.

Also, not denying the fact that these are research based on few users, it is not necessary that this will always hold well but most of time it will.

There is one more key point here is that there shold be more space between positive & negative action buttons so that users will take little more time to reach to negative buttons and thus will give them ample amount of time to thought and react.

I have tried to explain couples of points are based on my experience and from research papers.

Do comment, so that I can also learn more.

Regards Deepak Bajaj


A lot of applications have been shifting to use different styles for OK vs Cancel buttons. One common UI is to have the OK button but a traditional button whereas the Cancel is a link button. This gives a very clear visual distinction between the two and even though it leads the user to click OK, the visual distinction ends up highlighting the difference and helps the user pick the one they actually want.

I've seen this both in web and desktop applications.

  • 1
    Sam has a point here (which I was about to raise): the question mentions 2 buttons, but there might be a single one, tha positive OK or accept or whatever action. The other actions, like [cancel] but also other options like [clear all] or [whatever] need not to be buttons, and they are better off being another kind of click target. In this case it might be helpful to display them as buttons on hover, in order to communicate the user their hierarchy, but this is not essential.
    – Juan Lanus
    Commented Jan 19, 2016 at 21:13

Wow! Such a lot of answers arguing left or right.

I ran tests on this myself and found them to be statistically inconclusive.

The best answer I found was that it doesn't really matter which order they go it as long as the primary action is clearly marked - I always use a colourful button for [Do it]/go/submit/etc and a smaller text only button for [Don't do it]/cancel/clear/etc.

Very much like the 'Post Your Answer' and 'discard' buttons at the bottom of an answer form right here on UX StackExchange!

  • Finally an answer that talks about aesthetics and how important it can be Commented Sep 15, 2017 at 12:46

For ASP.NET web applications, after taking a lot of aspirin for dealing with default button issues (whatever will fire when the Enter key is pressed), I just put my default button on the left so that it is first in the markup.

Different browsers will handle multiple submit buttons differently when the Enter key is pressed (especially when the cursor is inside a text box at the time of Enter press). Some browsers will just use the first button in the markup to submit the form, which may not be what you want (especially if you need to do something on the server-side afterwards).

If you aren't using custom javascript to handle default button scenarios, and are relying on web browser default behavior, then you should probably put the default button on the left.


Just to clarify the reasoning:

It's considered "more correct" to place the main button (OK) on the exact corner of the dialog, since it's easier to hit (there have been several past questions/discussions about this).

However, it also depends on what the users are accustomed to - if you're creating a site or application for Windows users, you had better follow Windows standards.

Make sure that "Enter" on the keyboard is correctly associated with the OK - a lot of people will use that too.

  • 3
    How would it be easier to hit in the corner of a dialog? Dialog windows generally don't extend to the edge of a user's screen, so they can't use the same technique there. Or am I misunderstanding?
    – Rahul
    Commented Aug 30, 2010 at 8:17
  • 1. In my opinion, it's not only the physical screen that stops you - it's easier for us to follow the contour of an object.
    – Dan Barak
    Commented Aug 30, 2010 at 13:22
  • 1
    2. The corner is the END of the dialog, and it's easier to jump to the end rather than any point in between.
    – Dan Barak
    Commented Aug 30, 2010 at 13:23
  • Hmm, I dunno. Perhaps you could give a visual example?
    – Rahul
    Commented Aug 30, 2010 at 14:07

If posible, I would suggest omitting the cancel button altogether, thus solving your dilema. - It is sometimes unnecessary, and is often activated by mistake.

From http://www.nngroup.com/articles/reset-and-cancel-buttons/:

Most Web forms would have improved usability if the Reset button was removed. Cancel buttons are also often of little value on the Web.

Offer a Cancel button when users may fear that they have committed to something they want to avoid. Having an explicit way to Cancel provides an extra feeling of safety that is not afforded by simply leaving.

Cancel is mainly useful for multi-step dialogs where the user has progressed past one or more pages with actions. At this time, pressing the Back button will not undo these actions and it would be better if the user would click Cancel.


You can find an interesting opinion here; Anthony T. suggests that placing the "OK" button to the right of "Cancel" is better:

With the ‘Ok’ button on the right, the visual fixations are less and flow in one direction [...]

Compare that with the primary action placed on the right of the dialog box and the secondary action placed on the left. Users start with their eyes on the secondary action, and move their eyes to the primary action to click the button. This creates a total of two visual fixations in one direction, giving users a faster visual flow. Users fixate on each button only once and end on the primary action button. Putting the primary action left might make it easier for users to reach, but when you look at speed in terms of the user’s mental processes and visual fixations, placing the primary action on the right of a dialog box is actually faster.

  • 1
    +1 for an excellent article! I think another key point he makes is that platform consistency is not good enough; the suggestion to follow platform conventions for the sake of consistency is simply not good enough and leaves designers empty-handed.
    – M.A.X
    Commented Dec 5, 2012 at 19:18

Lol I can't help but laugh by many of these answers. It seems like a case of not seeing the forest for the trees. Like every UX problem fundamentally it depends on how the form is layed out. For example, Labels top, fields below or labels left fields beside. Look at the entire page and how a user's eyes flow down the form. Is there a clear line of sight to the final 'Submit' button?

As stated in a previous post Luke Wroblewski book about web forms Web Form Design: Filling in the Blanks contains some of the best advice in web form creation as well as a great paradigm of forms from a user perspective - Forms are a means to an ends and are tolerated because of the intended end result (ie purchasing something, creating an account to get access to somewhere etc). User test, AB test yes of course if you can. The ultimate goal being the easier your form is to fill out the better.


To me this would be the logical order:

<Left Right>

<Previous Next>

<Back Forward>

<Back Done

Do nothing Do it

Cancel OK

Except OK should be replaced with the actual action such as Save Delete Accept Exit or Send.

When I meet people arguing for putting OK on the left, I always ask them to place Left vs Right, Previous vs Next, and Back vs Forward, and let them argue why they put them in that order, before letting them argue why OK should be on the left.

  • 1
    This is a good example of how similar ideas are already arranged, and makes sense. Commented Dec 5, 2021 at 5:26

Ultimately (especially after reading all the above replies) I see this discussion boil down to platform convention vs. 'objective' usability. What I mean by 'objective' is how usable something would be for users who aren't familiar with any OS convention. More specifically:

OK on the right
This pattern wins hands down in the objective usability argument IF users aren't conditioned to the less usable windows convention (see article). As the article discusses, having the OK on the right aligns with our left-to-right reading convention, more efficient task flow, is a better corner target, also the fact that we think of timelines as running left-to-right (hence a 'back'/'cancel' on the right makes sense seeing as it's a back in time pattern).

OK on the left
Windows convention

It's an unfortunate reality, but poorly designed patterns (such as OK on the left) can become a convention and users will come to expect them. Trying to do something else, even if objectively it's a more usable pattern, will result in poor usability. A classic example is the metric vs. imperial measurement system - the metric system has everything going for it in terms of usability, easy of unit conversion, etc; but if you force small-town Americans to think in meters and centimetres when they're used to inches/feet you'll get poor usability and very frustrated users. I guess the lesson is to work very hard to make sure we never introduce poor conventions in the first place!

Personally when designing for the web I choose to put the OK button on the left, I also insist on stating my height in centimetres and my weight in kilograms, even when talking to imperial-minded folk. It's a war of attrition really, but slowly the imperial system will die off, and hopefully the windows 'OK on the left' convention will too :)

  • 1
    Similarly to your argument about "conditioning of users" who's been trained to use OK on the left, one can refute that opposite arrangement is very much the same conditioning, arguably found mostly in the Mac world.
    – Art
    Commented Dec 5, 2012 at 20:54
  • Completely agree, I'm not arguing in favour of the windows approach, simply stating that if you design for the windows world then you might have to go with convention over objective usability. Luckily in the Mac world the conditioning also aligns with what is the most objectively usable solution, so no problems there :)
    – M.A.X
    Commented Dec 5, 2012 at 22:58
  • 2
    I'd disagree that "OK-on-right" is 'hands down best objective UX' -- per this article mentioned elsewhere there's also visual continuity to consider -- if you're already scanning down the left side of a form, then "naturally" users start at the left side when they reach the action section, so placing primary action on the left would "make more sense".
    – drzaus
    Commented Nov 23, 2016 at 16:12
  • IMO, the article you refer is about dialog prompts (binary input) not forms. See lukew.com/ff/entry.asp?571 for an article about forms instead. Note that they also did user study instead of guessing about behavior of other people. Commented May 5, 2020 at 17:55

I'd go with "Ok" on the right. Because of western reading direction that goes from left to right. And "Cancel" wouldn't bring you ahead but "Ok" will.

But a totally different approach. Don't use "Ok" and write on the buttons what they do. For example "Save" or "Don't Save" doesn't require the user to read the description text. Saves time and prevents input errors.

  • Doesn't western reading direction suggest that the buttons should be put on the left? We don't use a lot of right aligned text anywhere. Commented May 5, 2020 at 17:56
  • 1
    In that sense, the left also resembles "the past" in LTR contexts.
    – straya
    Commented May 8, 2020 at 3:21

Of course there are plenty of arguments for and against both sides.

I would put it this way though. "Do you believe that negative-positive placement is the best? No or Yes?"

The point being that "Yes or No" flows better when spoken, which likely explains why positive-negative button order was chosen by Microsoft.

On the OTHER hand, negative-positive flow is often used in rhetoric and debating in order to add weight to the positive argument and keep it fresh in a person's mind. "Do you want to see your children suffer at the hands of the opposing party? Or do you want to vote for our party and secure your future?" And so on.

  • Apparently Apple put [Cancel] [OK] because they want to differentiate from Xerox Alto, so they wouldn't get sued in court for blatantly copied Xerox user interface.
    – dns
    Commented Jan 17, 2022 at 18:34

In order of priority, use the first available solution:

  • platform guidelines
  • start to end (where start for western languages is typically left, however can be different, e.g. arabic starts right and ends left)
  • the way your user's most expect

However in the case of screen readers and similar Accessibility tools, having the main action at the start (left in western cultures) can save such special-needs users a lot of time!


In my apps I'm using visual color for highlighting the action button purpose. Then no matter if it's left or right. I personally prefer to have the "ok" button on the right (because I'm right-handed and/or osx user - and actually this is link..)

  • big green button for validation
  • big red button for deletion
  • (big or not)gray button for cancel

I really like some of the sites where there is NO button (visually) for negative action, only a link. This way I dont have to waste time looking at buttons, I more-less know that the button does. And If i know i dont want to do what the pages wants me to, i take some time to see how would it be the best to go on (look for close button, cancel button)

so instead of:


there would be:

No, thank you! [Yes, please!]

This way there is not really important where you position your button, there is visually only one and therefore easy to locate.

  • 1
    Your second example is indeed very clear. However, do you have some reason to believe it's better in that order? For me, the best UI would have the positive action button first and cancel last, especially when positive action button is emphasized and the label clearly says what is going to happen. For example, Shred document Abort Commented May 5, 2020 at 17:59

Assuming that the decision needs to be made whether the positive action should be available on the left or on the right and disregarding the bias of using certain operating systems or physical apparatus (books), abstract constructs (wizard form flow) etc, the behavioral science seems to suggest that statistically leftmost option is chosen more frequently as a first choice.

This implies that placing a positive action (OK or explicit action label) on the left should be preferred if no other factors are considered.

Source: Is it only humans that count from left to right?


I suggest to switch buttons of the mouse too. In English and other languages Right is used as direction and positiveness. So we need to correct bad desision from the past, where the left button means 'confirm' and implement default action to the right button.

Also for the RTL reading languages the mouse buttons should remain as is - left as default action. I'm not sure what to do with top-to-bottom reading languages, but I'm open minded and will accept all suggestions from people who reads from top to bottom or bottom to top, or diagonally.

We are so smart these days. Am I right? ...Or am I left?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.