Brian
My feedback
13 results found
-
9 votes
Brian supported this idea ·
-
12 votes
An error occurred while saving the comment Brian supported this idea ·
-
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.
Brian supported this idea ·
-
75 votes
An error occurred while saving the comment Brian commented
This description text provides no value and actually interferes with the proper function of some user scripts (urcomments-enhanced for example). Please remove it
Brian supported this idea ·
-
10 votes
Brian shared this idea ·
-
23 votes
Brian shared this idea ·
-
39 votes
Brian shared this idea ·
-
1,235 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.
Brian supported this idea ·
-
154 votes
Brian supported this idea ·
-
51 votes
Brian supported this idea ·
-
175 votes
Brian supported this idea ·
-
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!
Brian supported this idea ·
-
24 votes
Brian supported this idea ·
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