[TIMOB-5339] iOS: get/setMessageID in Ti.UI.AlertDialog does not throw an error
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Invalid |
| Resolution Date | 2017-06-12T19:07:32.000+0000 |
| Affected Version/s | Release 1.8.0 |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | alertdialog, ios, parity, tbs-1.9.0 |
| Reporter | Natalie Huynh |
| Assignee | Ingo Muschenetz |
| Created | 2011-09-22T15:32:33.000+0000 |
| Updated | 2017-06-12T19:07:32.000+0000 |
Description
Steps to Reproduce:
1. Create an application with the following:
Ti.UI.createAlertDialog().setMessageid("abc");
2. Run application
Actual Result:
No Error
Expected Result:
should show you an error that the function setMessageid cannot be found
See Android bug
The way setters are done on Titanium:iOS is that it's dynamic. That is, there's no difference between foo.setBar(baz) and foo.bar=baz. I'm not sure we should make an edge case for this, because throwing an error for this would be the exception, not the norm.
Proposing we close this as 'won't fix.' The change would have to be deep (at the KrollObject level) and could make regressions. I'm having a hard time justifying such. Out of curiosity, what happens on Ti:Android for a random proxy when setFoo is invoked?
Closing ticket due to the time passed, lack of information and lack of progress. Any problems, please file a new ticket.