Confirmed users
368
edits
WebAPI/WebSMS: Difference between revisions
remove unread from SmsMessage and SmsFilter
No edit summary |
(remove unread from SmsMessage and SmsFilter) |
||
| Line 48: | Line 48: | ||
readonly attribute DOMString body; | readonly attribute DOMString body; | ||
readonly attribute Date timestamp; | readonly attribute Date timestamp; | ||
}; | }; | ||
Comments: | Comments: | ||
* ''unread'' property was considered but it requires a read/write ability so it will be added later | |||
* We have .sender and .receiver because someone can have multiple number or change numbers. We could merge them to .number if that seems necessary. | * We have .sender and .receiver because someone can have multiple number or change numbers. We could merge them to .number if that seems necessary. | ||
| Line 60: | Line 60: | ||
DOMString[]? numbers; | DOMString[]? numbers; | ||
DOMString? delivery; // whether "sent" or "received" | DOMString? delivery; // whether "sent" or "received" | ||
}; | }; | ||
Comments: | Comments: | ||
* ''unread'' property has been removed because it has been removed from SmsMessage. | |||
* When we will have MMS support, we would have to add a .type property to allow looking for SMS or MMS. | * When we will have MMS support, we would have to add a .type property to allow looking for SMS or MMS. | ||
* For the moment, there is no way to filter according to the content of a message because we didn't find a nice way to do it. This could be added later though. | * For the moment, there is no way to filter according to the content of a message because we didn't find a nice way to do it. This could be added later though. | ||