I don’t keep cookies between sessions on the beta server. Maybe that makes a difference?
Login, Open Relationship page, click Add relationship…
Do the steps on the current server and you get this:
(Note the second test was also from a “no saved cookies” browser)
I deleted all my cookies, logged back in and edited a release for relationships as in your beta example, and Artist is preselected. Make sure that you don’t have userscripts enabled. Check whether your latest relationship edits on beta were not about Area. If it still preselects Area, please create a ticket with more details about your setup (platform, web browser version, system/browser/website languages, any specific extension/setup) and a link to a page you experienced this bug.
Just went to a different browser, no userscripts on that one. Same steps as above to edit relationships.
Still starts up with Area. (And no, I was not editing Areas previously… this second browser has never had anything MB done on it)
Win10, Brave and Vivaldi, English UK.
But if no one else is seeing this then I guess it is just me.
It’s not just you.
(Bypass 20 character limit)
It just selects the first item in the list, and since they are sorted alphabetically this can vary depending on which UI language is active (for English it’s always area). Opened MBS-12915 for that.
I found a slight issue when trying the new editor out earlier today: there’s no longer a tooltip with the original name when you hover the mouse over an area, label or place that’s credited as something else.
It is likely that my language settings for beta was French while it was English for main.
Thanks, opened https://tickets.metabrainz.org/browse/MBS-12917.
I’ve noticed the search seems to ignore trailing space now. It was a nice shortcut to trigger the search:
Can reproduce:
Also recently filed
Is this intentional?
on the new beta, I’ve got a pretty big bug on mobile (Chrome), already a ticket
Works/recordings with a specific order appear rather random in the work column of the release relationship editor:
Previously they were ordered alphabetically:
When adding a relationship to a collapsed list it might be added to the collapsed portion and the user won’t see it was actually added unless the existing relationships are expanded.
Try steps at [MBS-11886] Series > Series 'subseries' relationship bug/strange behaviour - MetaBrainz JIRA
Old experience:
New experience:
Spotted and reported another seemingly sporadic issue:
And a problem when submitting no changes:
I added some early mockups to the ticket, have a look and let us know if any of this would solve the problem. Or if I’m missing the mark.
Looks pretty good, I personally currently prefer the ones where the difference is more obvious: different background in 4 & 5 and the lines in 7 & 8 (all of these also works best when zoomed out). It also looks a bit weird that the headline “performance” and the selectable “arranged/arranger” currently is on the same level. You’ve also highlighted how bad the indentation currently is, so increasing that is a minimum imo if you decide to do any changes, because it really helps a lot when distinguishing between the different options. Increasing the indentation + make sure that the headlines are not on the same level as selectable options might be the way forward? “Bold” is afaict now used to show the selected item, which I like because it matches how the relationships are shown after the pop-up window is closed, but this also means that it probably is not a good idea to make the headline “bold”. I also have no idea if you plan to introduce more colours here in the upcoming redesign, which could be an additional option to somehow make the distinction a bit clearer.
Some lines are headlines and selectable, so this isn’t a clear difference imo. I wouldn’t want some headlines to look really different when I’m scanning the page looking for groupings/headlines. Does that make sense?
I also thought more indentation seems a pretty clear way to improve this in general.
Oh, I didn’t realise that the real problem is that headlines can be selected. I guess this is similar to the old “guitar family” and “membranophone” problem then. It really only becomes a problem in edge cases like this where you have something that should be both noticeable (headline) and not be noticeable (can’t be selected) at the same time, which obviously is not optimal.
Increasing the indentation makes the difference much clearer, but there will be an inconsistency which means that some headlines are harder to spot than others. You went with only light-grey for “can’t be selected” which makes sense because that’s how most websites does it. In the old MB rel editor you combine light-grey text with a dark-grey background. Replicating the old MB css style (which also have bigger indentation) OR adding a new headline to “arranged/arranger” (all of the other selectable items are already on level 2) plus new unique css to the headlines, seems like the two best solutions to me.
Basically, there’s no such thing as a headline, in concept, right now. There’s “relationships that can be selected” (black) and “relationships that cannot be selected and are only used for grouping others” (grey), but they all live in the same tree. For example some entity combos (like artist-event) have a lot of top-level selectable relationships plus one used for grouping, and some (like event-recording) don’t have any grouping types at all. So, it’s kinda weird and it’s hard to decide “this is a heading but this is not” 
This is now out, thanks for all your help! That said, if some of you who weren’t usually using beta keep using it in the future, it will surely help us find more issues with our changes before they get released to everyone, so we’re thankful to anyone who decides to stick around as a beta tester 
It looks like a feature regression slipped through. IIRC previously it was possible to expand dates on relationships by adding them anew.
Edit by @yvanzo: now tracked as [MBS-12966] Regression: Specifying an attribute to a relationship duplicates it - MetaBrainz JIRA
Yes, my edit there. I commented on that earlier in this thread. Quite annoying, especially since batch-helping scripts no longer works.