Skip to main content
A
ashleyg1-Visitor
1-Visitor
July 11, 2016
Solved

Google Maps Widget bug using Master

  • July 11, 2016
  • 2 replies
  • 2062 views

Hi All,

I believe I have found a bug with the Google Maps widget but didn't want to log a case with PTC in case somebody had a solution?

It appears when using a Google Maps widget inside a contained mashup (in my case the contained mashup of a Master) the widget appears to be distorted as below:

Google Maps Widget Screenshot.jpg

Note: The above example uses geofencing which currently only has ONE region created. I am also using ThingWorx 7.1

The widget content should fill the whole space but instead just a square in the corner.

Best answer by Aanjan

Ashley, are you using any tabs or a popup as well? I tried reproducing on my end with the map on a Contained Mashup, and it rendered correctly. What browser are you using? I tried mine on Firefox; so if you didn't try it on Firefox, can you possibly give it a shot there?

2 replies

T
ttielebein5-Regular Member
5-Regular Member
July 11, 2016

What kind of display settings are being used on this mashup (with the Google Maps widget)? Is a size specified? Is it static or responsive?

I do not seem to see this issue with the Maps widget, but I am not using any kind of geofencing on mine, so that may be directly related.

A
ashleyg1-VisitorAuthor
1-Visitor
July 12, 2016

Hi Tori,

It is responsive however it appears launching in Firefox works but Chrome does not, rather inconvenient.

Thanks

Ashley

A
Aanjan5-Regular MemberAnswer
5-Regular Member
July 11, 2016

Ashley, are you using any tabs or a popup as well? I tried reproducing on my end with the map on a Contained Mashup, and it rendered correctly. What browser are you using? I tried mine on Firefox; so if you didn't try it on Firefox, can you possibly give it a shot there?

    A
    ashleyg1-VisitorAuthor
    1-Visitor
    July 12, 2016

    Hi Aanjan,

    It appears that launching the Mashup on Firefox fixes this problem, although it isn't idea, any idea why this is the case? Is there anything I can do to get it to work in Chrome?

    Thanks

    Ashley

    Terms & ConditionsAccessibility statement