need to respond with error objects in client api for 0x0 surfaces.
Bug #1604874 reported by
Kevin DuBois
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
New
|
Medium
|
Unassigned | ||
| mir (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
If creating a 0x0 surface, we should be sending an ErrorSurface back to the client api user.
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| Changed in mir: | |
| milestone: | 0.25.0 → none |
| importance: | High → Medium |
Revision history for this message
| Michał Sawicz (saviq) wrote | #2 |
| Changed in mir (Ubuntu): | |
| importance: | Undecided → Medium |
To post a comment you must log in.
I'm not sure we should need to treat this as an error when allocating zero is easy enough.
Why create error cases that people then need to handle when we can make it no error at all?