Open GoogleCodeExporter opened 8 years ago
Joe is heading out on a bike trip for the summer (DC to Seattle), and says he
won't
have time to fix up the maximize stuff (like this). So we should decide to
remove it
completely from the source (and branch it?) or try and fix and release.
Thoughts?
Original comment by pamela.fox
on 19 Jun 2008 at 11:01
Well, I haven't had a chance to look into it further, but I just kept noticing
it when looking for regressions in my
branches. I presume it worked in some browser at some point, and could be
fixed. Sometimes (with an empty
cache) the placement will be initially correct, but then the infowindow
reflows, and the button stays put,
reversing the proper locations of the respective buttons. Perhaps in another
browser or version the reflow
happened earlier. I'd just keep the issue open for now.
Original comment by lem...@gmail.com
on 19 Jun 2008 at 11:09
Original issue reported on code.google.com by
lem...@gmail.com
on 18 Jun 2008 at 4:32