Assigned
Status Update
Comments
ka...@google.com <ka...@google.com>
ka...@google.com <ka...@google.com>
ca...@google.com <ca...@google.com> #2
Thank you for the post.
Kindly provide a screen recording and steps to reproduce the issue encountered for further checking.
pl...@gmail.com <pl...@gmail.com> #3
#2, well just use any legacy map style (not migrated to next-gen yet) + gmap and a next-gen one + gmap, theres no extra steps
ca...@google.com <ca...@google.com> #4
Thanks for waiting.
Upon checking, it appears that this is a duplicate of
js...@gmail.com <js...@gmail.com> #5
That's funny that this is supposedly a duplicate of my post when in the comments section of my post I was told that the transparency bug needed to be posted as a separate issue. Google never forked it off as a separate post, as I asked them to do, and I never got around to doing it myself. I am getting tired of the run around. I think it would be best to leave this post by the OP active as it's own separate issue from my post... and then focus efforts on actually fixing bugs instead of making the comments section here ridiculously frustrating and annoying!
jh...@google.com <jh...@google.com> #6
You're correct, those 2 issues are related but different. The opacity/transparency feature will be considered first, then the stroke and width support will be reevaluated. For clarity, we are treating those as feature requests and can't provide an ETA.
js...@gmail.com <js...@gmail.com> #8
I also believe that they are bugs, as it is working fine with my legacy maps, but is broken in the next-gen cloud based maps. We are not asking for new features, just the standard functionality that was/is working with legacy maps to carry over to the new system.
jh...@google.com <jh...@google.com> #9
It's a close call. We'll be sure to post updates here either way when we have news to share.
js...@gmail.com <js...@gmail.com> #10
We are down to less than 17 days, and still silence from Google on fixing these bugs. Morally and physically repellent, disreputable and shady behavior!
Description
We recently migrated our legacy Map Styles to the "next-generation" of Cloud-based maps styling. In legacy Map Styles, 3d buildings had some transparency. Now, it seems impossible to render them with the same transparency.
Is this already known/excepted?
Is it possible to add a way to configure this?
Or support for colors with alpha in the console?
I added 2 screenshots in this issue, one osing quaterly + legacy Map Style, one using quaterly + "next-generation" Map Style