Brian
My feedback
14 results found
-
12 votes
-
14 votes
An error occurred while saving the comment -
274 votes
Hey,
Please note we're changing the status of this suggestion to Currently Not Planned since we finalized our plans for 2024 and this idea won't be implemented this year.
We hope to include it in our plans for later down the line.
Thanks!
An error occurred while saving the comment This is a very important feature
-
65 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
88 votes
Hey,
Please note we're changing the status of this suggestion to Currently Not Planned, since we finalized our plans for 2024 and this idea won't be implemented this year.
We hope to include it in our plans for later down the line.
Thanks!
An error occurred while saving the comment This description text provides no value and actually interferes with the proper function of some user scripts (urcomments-enhanced for example). Please remove it
-
11 votes
-
23 votes
-
39 votes
-
1,258 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
175 votes
-
54 votes
-
188 votes
-
85 votes
Hey,
We have looked at this suggestion, and in order to make some decisions about it, would like to kindly ask you to provide us with more data about it.
Please share some examples for when and where this restrictions apply? (use cases)
And any country you know relevant for it.
Thanks!
-
24 votes
This is a frequent cause of repeat map issue reports - an editor will fix a bad location pin, mark it solved, even verify it on their personal device, and the user will come back complaining in a new report that it's still not working. Particularly for newer editors this can be surprising if they don't know about the caching behavior. This could be as simple as implementing a TTL on cached recent drives, saved/bookmarked locations might need some more thought