Too many warnings hinders save

[jidanni]

Description

OK, we made an edit, pressed Save, entered our changeset comment, and...
Let's say there are 1000 warnings. I.e., the scrollbar indicator "A" is even smaller.
And say those warnings are all for bus routes and we have never rode a bus in our lives and they certainly are not our fault.

So we want to hurry up and find the final Upload button, but we must scroll past all those warnings first.

Yes we could grab the scrollbar and force it down.

But we don't edit often and are not sure that there is even a final Upload button at the end of all those warnings.

We try the X (B) but that just cancels our edit!

One solution would be a floating final Upload button, always visible.

Screenshots

[StC-OSM]

I was going to create a ticket to complain about missing warnings when I found this one 😄

I believe that the real issue here is the design choice to display all warnings, including those that were there previously. Ideally there would be an option to see them, but the default behavior would be to display only warnings triggered by the changeset that is being uploaded

[andrewharvey]

Ideally there would be an option to see them, but the default behavior would be to display only warnings triggered by the changeset that is being uploaded

Agreed, I've seen users completely new to OSM, feel overwhelmed and confused by these warnings unrelated to their changes.

[tyrasd]

Usually, iD only shows errors for features one has actually modified in the changeset (incl. newly created features). But especially for route relations, it can easily happen that a small change in a single road indirectly touches potentially lots of relations.

I agree that the UI is in such situations totally overloaded with warnings and not useful for the mappers. A simple solution would be to limit the number of displayed warnings and have an ellipsis at the end to indicate that there are actually more warnings.

[StC-OSM]

As discussed in another issue report, an admittedly less simple solution would be to only display the warnings that were not present before the changeset (i.e. not burden the contributor with the errors of their predecessors). Less simple, but more accurate. Especially in terms of route breaking.

[Ravish990]

Hi, My name is Ravish . I study at Polaris School Of Technology ,where I am in first Year. I am interest in contributing the organization and solving this issue. Will you please assign me the issue?? I love to fix it properly.

[tyrasd]

this issue is already being worked on by @AkashNegi1 in #10595

[Ravish990]

Ok I am unaware about it.
Any help feel free to reach out I am always excited for this.