<span style="color: transparent; display: none; height: 0; max-height: 0; max-width: 0; opacity: 0; overflow: hidden; mso-hide: all; visibility: hidden; width: 0;">
<blockquote>
<blockquote>
<p dir="auto">I strongly urge you to rethink this approach. Whilst I do not oppose using different colours depending on the age of changesets, the fact that older changesets are no longer clickable, makes scanning an area which does not show high activity, really painful: Large changesets covering several countries or continents - which have always been a nuisance - cause relevant changesets to drop down in the list making it necessary to perform a well-adjusted scrolling manoeuvre constantly keeping an eye on the bounding box color before one is finally able to click on the desired bounding box.</p>
</blockquote>
<p dir="auto">Older changesets are clickable unless covered by those large nuisance chagesets when they are inside the sidebar viewport. I'm not sure if changesets that cover the entire map viewport should be hoverable/clickable, but on the other hand there has to be some indication that they are intersecting the map view.</p>
</blockquote>
<p dir="auto">In principle, omitting changesets covering the entire map viewport sounds like an interesting idea. These changesets usually require to be looked at separately anyways. When verifying recent activities, one is in any case forced to look at the map using all sorts of zoom levels. Eventually, larger changesets are going to be included.</p>
<blockquote>
<p dir="auto">There's also an opinion that <a href="https://community.openstreetmap.org/t/better-osm-org-a-script-that-adds-useful-little-things-to-osm-org/121670/105" rel="nofollow">changesets outside of the sidebar viewport shouldn't be shown at all</a>. In this case you wouldn't see any older changesets.</p>
</blockquote>
<p dir="auto">This suggestion disconnects entirely from requirements of average contributors. And judging from the smiley, I doubt this was meant seriously.</p>
<blockquote>
<blockquote>
<p dir="auto">Besides, for people with issues of color-blindness, orange and red are too similar. I can't tell them apart without looking very carefully.</p>
</blockquote>
<p dir="auto">Orange and orange are even more similar. And again there's an opinion about "color noise", that is colors being too different.</p>
</blockquote>
<p dir="auto">Admittedly, the <em>same</em> color would have been a worse choice, but this cannot be an argument for keeping a poor choice of colors. Removing some red in the orange rendering the color more yellowish would probably be enough help for color-blind people (like myself). I don't understand the "color noise" issue - this recent update fundamentally relies on three sufficiently different colors in order to maintain useability of the history functionality altogether. It's not about map rendering, it's about detecting map changes.</p><p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/pull/5924#issuecomment-2817089708">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLP7RAOWL36GKMLCLPD22NUDVAVCNFSM6AAAAAB27N2S6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJXGA4DSNZQHA">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAK2OLLPD3LSJRWK3RB3CGD22NUDVA5CNFSM6AAAAAB27N2S6WWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVH5FQKY.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><openstreetmap/openstreetmap-website/pull/5924/c2817089708</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
</span>
<div style="display: flex; flex-wrap: wrap; white-space: pre-wrap; align-items: center; "><img height="20" width="20" style="border-radius:50%; margin-right: 4px;" decoding="async" src="https://avatars.githubusercontent.com/u/66620757?s=20&v=4" /><strong>limes11</strong> left a comment <a href="https://github.com/openstreetmap/openstreetmap-website/pull/5924#issuecomment-2817089708">(openstreetmap/openstreetmap-website#5924)</a></div>
<blockquote>
<blockquote>
<p dir="auto">I strongly urge you to rethink this approach. Whilst I do not oppose using different colours depending on the age of changesets, the fact that older changesets are no longer clickable, makes scanning an area which does not show high activity, really painful: Large changesets covering several countries or continents - which have always been a nuisance - cause relevant changesets to drop down in the list making it necessary to perform a well-adjusted scrolling manoeuvre constantly keeping an eye on the bounding box color before one is finally able to click on the desired bounding box.</p>
</blockquote>
<p dir="auto">Older changesets are clickable unless covered by those large nuisance chagesets when they are inside the sidebar viewport. I'm not sure if changesets that cover the entire map viewport should be hoverable/clickable, but on the other hand there has to be some indication that they are intersecting the map view.</p>
</blockquote>
<p dir="auto">In principle, omitting changesets covering the entire map viewport sounds like an interesting idea. These changesets usually require to be looked at separately anyways. When verifying recent activities, one is in any case forced to look at the map using all sorts of zoom levels. Eventually, larger changesets are going to be included.</p>
<blockquote>
<p dir="auto">There's also an opinion that <a href="https://community.openstreetmap.org/t/better-osm-org-a-script-that-adds-useful-little-things-to-osm-org/121670/105" rel="nofollow">changesets outside of the sidebar viewport shouldn't be shown at all</a>. In this case you wouldn't see any older changesets.</p>
</blockquote>
<p dir="auto">This suggestion disconnects entirely from requirements of average contributors. And judging from the smiley, I doubt this was meant seriously.</p>
<blockquote>
<blockquote>
<p dir="auto">Besides, for people with issues of color-blindness, orange and red are too similar. I can't tell them apart without looking very carefully.</p>
</blockquote>
<p dir="auto">Orange and orange are even more similar. And again there's an opinion about "color noise", that is colors being too different.</p>
</blockquote>
<p dir="auto">Admittedly, the <em>same</em> color would have been a worse choice, but this cannot be an argument for keeping a poor choice of colors. Removing some red in the orange rendering the color more yellowish would probably be enough help for color-blind people (like myself). I don't understand the "color noise" issue - this recent update fundamentally relies on three sufficiently different colors in order to maintain useability of the history functionality altogether. It's not about map rendering, it's about detecting map changes.</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/pull/5924#issuecomment-2817089708">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLP7RAOWL36GKMLCLPD22NUDVAVCNFSM6AAAAAB27N2S6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJXGA4DSNZQHA">unsubscribe</a>.<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAK2OLLPD3LSJRWK3RB3CGD22NUDVA5CNFSM6AAAAAB27N2S6WWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVH5FQKY.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><openstreetmap/openstreetmap-website/pull/5924/c2817089708</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/pull/5924#issuecomment-2817089708",
"url": "https://github.com/openstreetmap/openstreetmap-website/pull/5924#issuecomment-2817089708",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>