css – Why should “cancel” and “confirm” button have the same size?

Cancel and Confirm typically just happen to have same size buttons. There’s really no UX principle supporting same size primary and secondary buttons

In fact, a larger confirm button is preferred to emphasize the primary action. This is why a lot of cancel and undo actions on the web are styled as a link (e.g. UX.SE’s post answer form) to give the primary action more weight.

You can read more about visual weight from the article referenced by @DasBesto https://uxmag.com/articles/visual-balance-and-weight-allocation-for-usability

Then why are cancel and confirm buttons usually the same size?

  1. The word “Cancel” and “Confirm” have very similar length.

Buttons length by default are determined by the length of its content. Since Cancel and Confirm are very similar in length, you get similar size buttons.

  1. Buttons on touch screen needs to be large.

On a mobile device, you need large tappable buttons. With a modal, to facilitate tapping, you make the buttons span the entire width. Cancel and Confirm are made the same size as a compromise to ensure both buttons are easy to tap on. This is okay because color also provides strong visual weight. As long as your Confirm button color make it stand out from your Cancel button, having the two button be the same size isn’t that big a deal.

dnd 3.5e – What would happen if you try to mount a creature of your own size?

The rules state the following in terms of suitable mounts:

(The DM has) the final decision on what is or is not a suitable mount. At its most basic level, a mount should have the following characteristics:

Able and willing to carry its rider in a typical fashion. (A camel is able and willing. A tiger might be capable but may not be willing. A giant might be willing but not truly able.)
At least one size category larger than the character. Also, a flying mount can carry no more than a light load aloft.

Emphasis mine. However, what are the consequences of trying to mount a creature of the same size or smaller than the character in question? Especially if the would-be mount otherwise does have the strength to carry the would-be rider?

gui design – When creating a GUI wizard, should all pages/tabs be of the same size?

Wizard vs. Tabs
Use a Wizard, when you want to guide the user through multiple requried steps.
Use Tabs when the user can select an arbitrary tab, make changes, and then commit them without looking at the other tabs.

I always find “Tabs with Back/Next” awkward. I understand the idea to provide a little “ramp” between novice and advanced users, but in most cases I’ve seen, the design of the individual pages isn’t suitable for novice users.


For a wizard, it’s not just size – the user should have the impression he interacts with the same window all the time. This is commonly achieved through a header and other control elements in the same position throughout all pages, and same size.

Example: Installshield violates the “same window” metaphor pretty badly (though it’s not too obvious): each page is a new modal dialog, centered on the primary monitor. So move the window to another position, click next, and bam, your window is back where it was. Aaaargh!

In a wizard, a changing form size is quite awkward for users. It’s like holding his hand, but you are constantly dancing around him. In more serious terms: the user action (clicking “Next”) has an unexpected side effect (“Window size changes”). This decreases the users perceived control over the software.

I’d argue that even for tabs, changing sizes are awkward. First, it looks shitty – which subjective. Second, if you position the window containing the tabs so that they are in the corner of a screen to reveal another document on your desktop, an you switch to another page, either part of your dialog vanishes, or it jumps further into the desktop, potentially covering other things.

(Full disclosure: I am working on an app which does that, and it’s my fault. Watching users pull around that poor little dialog makes me cringe. It’s one of those little speed-bumps that build up annoyance).

If the choice is between “a little crowded” and “almost empty”, it’s usually fine. Empty space looks good. Just having a large prominent window with a single input field makes a clear statement: this is your next step, and it’s darn easy. That’s exactly the message you want to send with a wizard.

Why do tempdb spills still occur even with good row and data size estimates (better than actuals)?

We’re seeing tempdb DB spills for some hashing operations. If the estimates are indeed good as shown what would be the next thing(s) to look for? Looking for a generic answer without having to resort to the specifc query.

This is part of an SP. Just switched to 2019 version to see if it would auto adjust but still getting spills so far.

Microsoft SQL Server 2019 (RTM) – 15.0.2000.5 (X64)

Hash Match Warnings

Change size of modal in wizard experience

I am building a wizard experience to guide a user through a complex setup flow. In the flow, some steps require more space and some require less space. Does it make sense to change the modal size on each step or to keep it the same?

Could you justify the answer with a reason?

What is a typical Notability’s file size?

What is a typical, “notes only”, Notability’s file size?

What if the notes contains that 20-minutes lecture/audio clips – what is the size for each of these attachments?

What is the probability of having forks in PoW given different network size (miners count)?

Given a network of k miners, what is the impact of k on the probability of having forks in Bitcoin or any PoW-based blockchain?

It is clear for me that a network with fewer miners will have less probability of having a fork than a network with higher number of miners.

Is there any mathematical formula that shows this relation?

html – How to make this div element the size of the img contained within it? [css]

I am attempting to create a tooltip, to appear when hovering on an image within a table.
However when I add the div to put a container for the tooltip, it adds extra spacing to my table, as seen in the first row (not applied to subsequent rows).

Why is the div 118 x 66 size as shown instead of the size of the image within it (59×59
)? It creates unnecessary spacing.

Oversized horitionzal dimension


CSS for tooltip

Tooltip in action

size – SQL Server : database free space vs data file free space

Stack Exchange Network

Stack Exchange network consists of 177 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

Sensor size and SNR – Photography Stack Exchange

Let’s say here we have two sensors, one bigger and one smaller, both of them have same pixel size and everything is identical except the sensor size. And now we are photographing the same object with the two sensors using identical camera lens. Bigger sensor has larger FOV compared to the smaller one and the total light collected will be greater. Then, we crop the image captured by the bigger sensor to match the image captured by the smaller sensor. Will the SNR for both image be the same? Because a lot of sources on the Internet stated that larger sensor is better because it will capture more signal, resulting in less noise. But I don’t see other advantages here except the FOV part, in which larger sensor has to spend less time on capturing a particular object that the smaller sensor may have to use mosaic method on.

The concept is explained here at 10:53 but I don’t really get it.