-
Notifications
You must be signed in to change notification settings - Fork 1.1k
google chrome cluster F on InfoWinow #960
Comments
Will we need something like this https://github.com/ded/bowser or is it provided in angular? |
are you thinking something like |
Changing
to
works |
@aesnyder yup |
Where do you download older versions of chrome? |
from my research you cant, client has 38 and one of my devs on my team as well... |
not sure if it is safe |
maaybe, brew cask? |
what is "safe" anyways? |
lol, yeah try out either one. Got the command to install an older chrome w/ cask? Vs point and click on the url fomr uptodown |
I opened it from the dmg, and it showed up 39 when i clicked 'about' |
looking for cask command now |
yeah dmg didnt work, but thats cayse chrome is using the same "Application Support Directory" |
IE cache |
meh, cant get an oldversion from cask either |
firing up my ubuntu vm, maybe it is on an older |
ehh, im just gonna pull in bowser and make an angular service. We can unit test it and cross fingers and then drink heavily. |
down |
oh wait, i think browserstack would work |
our subscription lapsed... |
Does your one developer still have 38? Can he verify that the InfoWindows still work with evalAsync without defer? |
Wow Browserstack rocks. Anyways 38 has same problem maybe GoogleMaps fixed this? Not sure. |
Same with 37 so looks like something we fixed or broke not sure. Can we do this without bowser? |
yeah my dev saw that with evalAsync in 38 |
im not sure how its fixed, which makes me reticent to say that it is fixed |
Does evalAsync return a promise? How do we know when it is done? Both of these functions are ( or were) returning $evalAsync. To me it seems there is a problem with the creation not completing before showWindow actually happens. |
Looks like we started having repaint issue after, 27c2d27 I am gonna try removing the evalAsyncs and see if that issue works. I think the evalAsync in createGWin may be causing problems. |
that might be the case, it doest return a promise but my understanding is that the callback will only execute after the dom has been manipulated by angular... in my mind kind of like animation frame |
though as i read it this may not be correct, when called from a controller it happens before the view is rendered. i believe that the maybeRepaint should actually be triggered after render to get the height to render properly... |
@aesnyder has got chrome 38 to reproduce the original error reliably via browserstack, so this is most deff a chrome issue. Looks like we will pull in bowser to deal with it. |
So it appears google chrome version 39 has fixed our CSS repaint woes.. However our repaint fix now breaks google maps on firefox and on the latest chrome.
Lovely art:

The text was updated successfully, but these errors were encountered: