i spent 3 hours debugging error , in end narrowed down (i think) variable name. i using initmonths (initial months) caused unpredicatable errors when changed imonths worked! i can understand preventing use of init on it's own surprised if prevented part of variable name. bug or feature? it's not bug if it's related name being overlap. there's part of arc used know when retain counts should updated, , may running that. similar rules apply use new @ start of names (for same reason). it's easy , wise steer clear of using init @ start of names unless it's init function. i can imagine issue related arc getting involved shouldn't , takes while called shouldn't, weird. i expect issue else , name change had other effect. worst case means have memory issue , changing name has changed memory footprint of code you've moved bug somewhere else (or along lines).
tried switch new router in version "@angular/router": "3.0.0-beta.2" in combination "@angular/*": "2.0.0-rc.4", following official docs on componentrouter. however, i'm facing issue when trying load app default homecomponent: cannot find primary outlet load 'homecomponent' it seems has using templateurl , external html file instead of using inline template style. homecomponent not shown in window , error printed console. however, when use link home component gets shown second hand. as change from templateurl: 'home.html' to template: '<router-outlet></router-outlet>' error gone, homecomponent shown , routing works expected. is known issue? work using templateurl? there have respect work? the problem was, due app loading screen, <router-outlet></router-outlet> did not exist yet, due race condition. if need hide html part containing outlet, use [hidden] instead o...
i'm using selenium test appllication running on firefox browser, when want click on button selenium, don't find it. find strange since can see element eye. have tried multiple method worked other exemple : wait.until(expectedconditions.visibilityofelementlocated(by)) wait.until(expectedconditions.presenceofelementlocated(by)); (i use xpath in path variable, , i'm sure correct) setting implictlywait on driver putting thread.sleep(1000) then again, post here because don't understand why selenium not see element diplayed on browser. important information maybe giving me proper answer html dom dynamically generate websocket triggered javascript event. edit 1: <button type="button" class="btn btn-xs btn-block btn-stroke" id="252_button"> delete </button> the element i'm trying access. use xpath it. it's not in iframe element. to access element did method supposed find , click on giving xpath in para...
Comments
Post a Comment