The Macromedia–Adobe patent dispute produced verdicts favoring both companies in May 2002, followed by a settlement that summer. To understand the history, separate Adobe's claims, Macromedia's counterclaims and the additional California case. A headline announcing a trial victory describes one event within that larger sequence.
Identify the court, patent and procedural step
The published Delaware claim-construction opinion, 201 F. Supp. 2d 309 (2002), concerns the meaning of disputed language in Macromedia's patents. It discusses sound-waveform editing and automatically updating blended graphic elements. A claim-construction opinion supplies the court's interpretation of patent terms; it needs to be read alongside later findings about the accused products and the subsequent disposition of the litigation.
| Proceeding | Patent subject | Identifiers |
|---|---|---|
| Adobe's Delaware claim | Tabbed palettes | U.S. 5,546,528 |
| Macromedia's Delaware counterclaims | Blended graphic elements and sound-waveform editing | U.S. 5,467,443; 5,151,998; 5,204,969 |
| Macromedia's California action | Draw-based web-page editors and hierarchical website editors | U.S. 5,845,299; 5,911,145 |
Adobe's first-quarter 2002 filing records the original Delaware suit in August 2000, the counterclaims in September 2000, and the separate California suit in October 2001. These patents concerned particular claimed methods. Describing the dispute as ownership of all interface tabs, all graphics blending or all sound editing would exceed that record.
Two May verdicts, followed by unresolved motions
In its filing for the quarter ended May 31, 2002, Adobe reported two Delaware jury outcomes:
- May 3: the jury found Macromedia had willfully infringed Adobe's tabbed-palette patent, found the patent valid and awarded approximately $2.8 million.
- May 10: the jury found willful infringement of Macromedia's blending and sound patents. Adobe described approximately $3.7 million in blending damages and $1.3 million in sound-related damages, while also reporting that one sound patent was found invalid.
The filing said both sides were challenging findings and described post-trial questions about damages and injunctions as unresolved. Those qualifications belong with the reported verdicts. The figures above preserve Adobe's rounded amounts; adding them creates only a rounded arithmetic total, not an independently established final payment.
The combination of infringement and invalidity findings is a reason to read the particular findings and later rulings carefully. One label such as “won” suppresses which patent, claim, issue and remedy was decided. This article reports the historical record; it offers no assessment of a present product's patent position.
The dispute ended through settlement
Adobe's following quarterly filing states that the parties reached a settlement resolving the Delaware and Northern California patent disputes on July 17, 2002, with confidential terms. This later filing changes how the spring litigation reports should be read: their expected future hearings describe a stage before the resolution.
The August 1, 2002 California dismissal order, Case C 01-3940 SI, records dismissal of the claims and counterclaims with prejudice. Each party was to bear its own fees and costs, and the court retained jurisdiction to enforce the July 17 settlement agreement. That order provides a concrete endpoint for the California action.
An accounting reversal describes a change in the company's books. Confidential settlement terms limit what can be concluded about the full commercial bargain. The public records cited here support settlement and dismissal, while leaving the confidential terms undisclosed. They do not support a simple calculation of what one company ultimately paid the other by subtracting the reported jury awards.
A reliable way to read a litigation timeline
Build one row per event with the court, case, patent or claim, document date, event date and procedural effect. Keep allegations, judicial interpretations, jury findings and settlement disclosures in separate fields. This preserves meaning when a later document changes the practical status of an earlier result.
- Start with the precise issue. Here, the Delaware construction opinion interpreted disputed claim language.
- Find the next procedural record. The May filing reported verdicts and pending challenges.
- Check later filings and orders. The summer records report settlement and dismissal.
- Retain the source's limits. A company's disclosure is its account; a court order establishes what that order actually directs.
- Keep unknown terms unknown. Confidential consideration and unreviewed docket details should remain explicitly unresolved.
For example, “Adobe reported a $2.8 million jury award in May” and “the parties settled the disputes in July” can both be accurate. The second statement supplies the later outcome needed to interpret the first. Neither establishes a new rule about all software interfaces.
This is a compact history based on the cited court opinions, dismissal order and company disclosures, rather than a complete docket reproduction. For another example of separating a platform's public promises from later events, read the RealNames closure case study.