Assigned
Status Update
Comments
an...@google.com <an...@google.com> #2
Thanks for alerting us to this issue. We verified it and added it to the list of things to keep track of. We cannot give details on the timeframe, but please star this issue to be notified of updates.
ni...@gmail.com <ni...@gmail.com> #4
Hi, is there any news about this issue?
an...@google.com <an...@google.com>
bk...@gmail.com <bk...@gmail.com> #5
Any updates?
vl...@gmail.com <vl...@gmail.com> #6
I'm wondering too, any updates?
bk...@gmail.com <bk...@gmail.com> #7
bump, updates?
bk...@gmail.com <bk...@gmail.com> #8
Is anyone even looking at any of these tickets?
vl...@gmail.com <vl...@gmail.com> #9
Any updates?
bk...@gmail.com <bk...@gmail.com> #10
Unfortunately, this bug seems to be forever forgotten :(
The problem is that, by default, when two pins have the same latitude, they get the same z-index which the bug causes to overlap each other.
I was able to resolve the issue by manually managing my own dictionary of markers and their z-index's similar to how its done by default (vertically lower based on latitude) with the exception that when there are two pins are close enough to overlap at the same latitude, I manually increase the z-index on one of them.
Hope that helps anyone else until Google decides to acknowledge this, let alone actually fix it.
The problem is that, by default, when two pins have the same latitude, they get the same z-index which the bug causes to overlap each other.
I was able to resolve the issue by manually managing my own dictionary of markers and their z-index's similar to how its done by default (vertically lower based on latitude) with the exception that when there are two pins are close enough to overlap at the same latitude, I manually increase the z-index on one of them.
Hope that helps anyone else until Google decides to acknowledge this, let alone actually fix it.
wo...@google.com <wo...@google.com> #11
Hello all, sorry for the delay in communications.
No, this bug is not forgotten :)
However, we cannot give details on the timeframe, but please star this issue to give it higher priority when we look at bugs.
No, this bug is not forgotten :)
However, we cannot give details on the timeframe, but please star this issue to give it higher priority when we look at bugs.
vl...@gmail.com <vl...@gmail.com> #12
Any timeframe on this bug please? You can do it Google, we believe in you :)
vl...@gmail.com <vl...@gmail.com> #13
Hello. Still nothing Google?
ka...@google.com <ka...@google.com> #14
Just a quick update that we were not able to look at his issue to date, but
bubbled it up the engineering triaging queue
Thanks for your patience...
bubbled it up the engineering triaging queue
Thanks for your patience...
ga...@gmail.com <ga...@gmail.com> #15
Still waiting for a fix!
Description
expected behavior: The text for the markers that get covered should be hidden.
actual behavior: The text for all labels is shown overlapping each other in front of the markers.
JSFiddle (modified from another one):
If you zoom close enough that the markers are not in the same spot anymore, the labels z-indexes get fixed.