1. ProCD v. Zeidenberg (1996, US Federal Court)

Key Issue:

Whether electronic or software-based acceptance (including selections in digital interfaces) creates a binding contract even if the user later claims misunderstanding.

Facts:

• ProCD sold software with licensing restrictions.
• The terms were shown after purchase inside the software (shrinkwrap model).
• User claimed he was not bound because he did not explicitly agree at checkout.

Held:

The court held the contract valid and enforceable.

Legal Principle:

• Acceptance can occur through conduct, not just explicit verbal agreement.
• If a user proceeds after being given a reasonable opportunity to review terms, they are bound.

Relevance to Drop-down Errors:

If a user selects a wrong option in a menu (e.g., “premium plan” instead of “basic plan”), courts may treat it as binding conduct, unless:

• the interface is misleading, or
• there is a clear system error.

👉 This case supports strict liability on user selection mistakes in structured systems.

2. Specht v. Netscape Communications Corp. (2002, US Second Circuit)

Key Issue:

Whether users are bound by terms not reasonably visible during online interaction.

Facts:

• Users downloaded software from Netscape.
• Terms were located below the download button (not immediately visible).
• Users were not required to click “I agree.”

Held:

No valid contract was formed.

Legal Principle:

• “Reasonable notice + affirmative assent required.”
• Hidden terms or unclear UI placement = no binding agreement.

Relevance to Drop-down Errors:

If a dropdown menu:

• auto-selects options,
• hides critical pricing/terms,
• or misleads users visually,

then courts may say:

there was no true “meeting of minds”

So, a mistaken selection may not bind the user if the system design is not transparent.

3. Hill v. Gateway 2000 Inc. (1997, US Seventh Circuit)

Key Issue:

Whether contract terms shipped after purchase are binding.

Facts:

• Customers ordered computers by phone.
• Terms inside the box said arbitration clause applied unless returned within 30 days.

Held:

Contract was valid; terms were enforceable.

Legal Principle:

• Acceptance can occur by retaining goods without objection
• “Rolling contract” concept is valid in consumer transactions.

Relevance to Drop-down Errors:

This case is often used to justify that:

• user selections (even mistaken ones) are binding if system clearly allows correction period.

In dropdown systems:

• If the platform allows confirmation before final submission, responsibility shifts to user.

4. Feldman v. Google, Inc. (2007, US District Court)

Key Issue:

Online click-based agreements in advertising systems.

Facts:

• Plaintiff used Google AdWords.
• He claimed he did not understand billing terms.
• He clicked “I agree” during account setup.

Held:

Contract was enforceable.

Legal Principle:

• Clicking “I agree” = strong evidence of consent.
• Courts do not excuse misunderstanding if interface is clear.

Relevance to Drop-down Errors:

If a user:

• selects “bulk order = 1000 units” instead of “100 units,” or
• chooses wrong billing tier in a dropdown,

courts often treat it as:

user responsibility unless system ambiguity exists.

This case strongly supports binding effect of UI selections.

5. Trimex International FZE Ltd. v. Vedanta Aluminium Ltd. (2010, Supreme Court of India)

Key Issue:

Whether electronic communications and informal digital negotiations can form binding contracts.

Facts:

• Parties exchanged emails and digital communications for sale of goods.
• No formal signed contract was executed.
• One party tried to back out.

Held:

A binding contract existed.

Legal Principle:

• Contract can be formed through offer + acceptance via electronic communication
• Courts look at intent and conduct, not formality

Relevance to Drop-down Errors:

Indian courts apply a practical approach:

• If system clearly shows selection + confirmation → binding contract exists
• But if the system allows confusion or ambiguity → mistake may be recognized

So, dropdown errors may be excused only if:

• there is evidence of system ambiguity or miscommunication

6. Hartog v. Colin & Shields (1939, UK King’s Bench)

Key Issue:

Unilateral mistake in contract formation.

Facts:

• Seller mistakenly quoted price per pound instead of per piece.
• Buyer tried to enforce the cheaper mistaken price.

Held:

No contract at mistaken price.

Legal Principle:

• If one party knows or should know of the other’s obvious mistake, contract is not enforceable.

Relevance to Drop-down Errors:

If a user accidentally selects:

• “₹9,999” instead of “₹99,999”

and the system or seller clearly knows it is a mistake, courts may:

• refuse enforcement at mistaken value.

This is very important for UI errors involving pricing dropdowns.

Core Legal Takeaways (Drop-down Menu Errors)

Across jurisdictions, courts balance:

1. User responsibility

• Clicking/selecting = presumed intent
• Mistakes usually bind the user

2. System design responsibility

• Poor UI, hidden terms, confusing dropdowns can invalidate consent

3. Knowledge of mistake

• If other party knew or should have known of error → contract may fail

4. Electronic contract validity

• Online selections are legally equivalent to physical signatures in most jurisdictions

Final Summary

Drop-down menu selection errors are generally treated as:

• Binding contracts if UI is clear and confirmation exists
• Void or voidable if mistake is obvious or system is misleading
• Non-binding if no proper notice or assent is proven