[ALOY-929] Widget/Require includes references to child elements targeted for other platforms
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2014-01-20T15:28:58.000+0000 |
Affected Version/s | Alloy 1.3.0 |
Fix Version/s | Alloy 1.4.0 |
Components | n/a |
Labels | qe-closed-3.3.0, qe-testadded, require, widgets |
Reporter | Fokke Zandbergen |
Assignee | Tony Lukasavage |
Created | 2014-01-15T11:55:16.000+0000 |
Updated | 2016-09-26T09:40:15.000+0000 |
Description
Given a view like this:
<Alloy>
<Widget src="foo">
<Window id="a" platform="ios" />
<Window id="b" platform="android" />
</Widget>
</Alloy>
For both iOS and Android the widget gets passed a children
property including references to both $.__views.a
and $.__views.b
, with one of them of course not existing, so giving null
in the widget when looping through them.
Moving this ticket to engineering for further evaluation and prioritization as it appears to be a legitimate issue and not related to Titanium.
PR: https://github.com/appcelerator/alloy/pull/301 test app: https://github.com/appcelerator/alloy/tree/master/test/apps/testing/ALOY-929 Functional test:
Run the test app.
You should see output once it loads in the console.
The output should list only one child (results are from an ios run)
Prior to this fix, there would be 2 children in the printed list. One child would be defined, the other would be
Verified the FIXED with: Appc-Studio:3.3.0.201405121247 sdk:3.3.0.v20140513191712 acs:1.0.14 alloy:1.4.0-dev npm:1.3.2 titanium:3.3.0-dev titanium-code-processor:1.1.1 xcode:5.1.1 Device:Iphone5s(v7.1.1),Nexus7(v4.4.2) Working as expected. Hence closing.
Issue still there with formfactor, child of zero come null with this case