[TIMOB-23813] Windows: Relative images paths are not relative to Resources dir, not current JS file
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | Release 6.1.0 |
| Fix Version/s | n/a |
| Components | Windows |
| Labels | n/a |
| Reporter | Chris Barber |
| Assignee | Kota Iguchi |
| Created | 2016-08-24T02:03:45.000+0000 |
| Updated | 2017-09-21T01:39:36.000+0000 |
Description
TIMOB-7004 states there there is a bug in Android where relative images are not loading correctly, however it's the opposite. The images are loading in Windows (and iOS) when they should not be.
In TIMOB-7004 test case,
app.js will require('ui/homeView.js') which creates an ImageView with a relative path. On Android, an image path of commonimages/home-home.png will try to load ui/commonimages/home-home.png. On Windows (and iOS), it appears to treat relative image paths as absolute paths, which is not correct.
No comments