Assigned
Status Update
Comments
la...@google.com <la...@google.com>
la...@google.com <la...@google.com> #2
Information redacted by Android Beta Feedback.
da...@weaveworld.com <da...@weaveworld.com> #3
Same issue here on qpr 3.1 on pixel 7 pro. Just started out of the blue on November 23 or 24.
la...@google.com <la...@google.com> #4
Unenrolled from beta, reset pixel 7 pro and did all updates. Ghosting, streaking, artifacts still present in public android 13. Green screen flashes when turning phone on or off occasionally.
la...@google.com <la...@google.com> #5
Same issue here on latest beta but I also have image ghosting on my screen. Icons and text have a ghosted image that bleeds down the screen.
da...@weaveworld.com <da...@weaveworld.com> #6
Issue still existing on public android and initiated a replacement front the Google Store.
Description
#IMPORTANT: If your production system or service is down file a Severity 1 support case at console.cloud.google.com/google/maps-apis
======================================================================== #REMINDER: Please do not disclose any PII. Some examples of PII are email address, IP, contact number, any part of name, project numbers and billing accounts. Comments or attachments that include PII will be removed and restricted from public viewing as it may violate our security and privacy policies.
Please refrain from emailing a reply to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but not API keys or client ID credentials.
To learn more about personal data, visithttps://en.wikipedia.org/wiki/Personal_data
Issue report
If you're seeing an issue in uploading data please provide a SAMPLE of the data which reproduces the issue. Also please refer to the documentation about the Dataset requirements.
If your issue is something else please describe the issue in as much detail as possible with steps to repeat the issue.
I've added a dataset to a map and the cursor always changes to a pointer when the mouse moves over it. I asked your Cloud AI how to turn that behaviour off and it said to use 'clickable: false' in the styling, but that threw an error - no such function. Then it suggested that I should turn off all interaction via click and mouseover handlers, which I did, but it made no difference to the mouse cursor. Then your Cloud AI gave up, and said I'd need to cover the entire map with another layer, which seems silly.
Here's the class that implements the dataset:
export class DatasetLayers { constructor(map) { this.map = map this.layers = new Map() this.datasets = [ { // Holkham Park id: '9a1199de-19c6-483d-add8-4c3f24cd60a4', style: { fillColor: "#b8d8c0", fillOpacity: 1, clickable: false <- AI's first suggestion, but this doesn't work } } ] }
initialize() { this.datasets.forEach(dataset => { const layer = this.map.getDatasetFeatureLayer(dataset.id)
} }
AI then suggested this:
initialize() { this.datasets.forEach(dataset => { const layer = this.map.getDatasetFeatureLayer(dataset.id);
}); }
...which didn't work either. Then it suggested this:
initialize() { this.datasets.forEach(dataset => { const layer = this.map.getDatasetFeatureLayer(dataset.id);
}); }
And that didn't work either.
This seems like a glaring omission. AI suggested I report it to you as a bug.
Is there any straightforward way to prevent the cursor from changing to a pointer when moving over a dataset element? Or is this functionality missing from the API?
Thanks
Daryl