Il pulsante con segno di spunta dovrebbe essere nascosto agli utenti che non possono deselezionare le risposte corrette

Ciao al team di Discourse-solved,

Suggerisco delle modifiche all’UX: il pulsante con il segno di spunta dovrebbe essere nascosto agli utenti che non possono annullare la marcatura delle risposte corrette.

02%20AM

L’unica parola visibile dovrebbe essere SOLUZIONE.

Grazie.

1 Mi Piace

I disagree - I think the filled box is an important part of the styling highlighting the post.

13 Mi Piace

@riking

Having a checkbox tells users that I can uncheck it. If I am not the OP or admin, I shouldn’t see the checkbox. Only OP or admin should see checkbox because that action is only for them.

For everyone else, they should only see the word “SOLUTION”.

We can add additional highlights by making the background of the post ‘Green’ or have additional highlights around it. But not using the checkbox.

UX wise, having a checkbox for the readers is not the proper way.

To the discourse-solved developers, i’m not a ruby dev, but how can i modify this in code in case I want to remove the checkbox in my site for readers not OP/Admin? What part of the code handles this?

Thank you. :slight_smile:

1 Mi Piace

You can hide it by adding the following line of CSS to your theme:

.actions button.accepted {display:none;}

PS: this does show there’s a slight alignment issue with the ‘Solution’ text:

image

4 Mi Piace

Thanks @bartv for the suggestion.

But the problem with that solution is it also hides the checkmark to OP or admin who should have the ability to uncheck it.

Ah true. Perhaps you could dig into the CSS a bit more to make the selector more specific and avoid this.

I was trying to do that and realize that this isn’t possible because you can’t add any conditions (if/else) in the CSS. The only way to make it work is editing it directly thru the plugin code.

To everyone that helped, thanks.

I was able to modify the plugin code already:

Here’s what I did:

For OP:
Instead of just the checkmark, I added this button - “This solved my question” which is more visible to the OP or readers.
24%20AM

Also, if OP wants to change his/her answer, this is what he/she sees:

42%20AM

Now, if I am not OP or admin. Here is what I see:

57%20AM

Again, thanks for those who have created this plugin. :slight_smile:

8 Mi Piace

I actually like this change quite a bit @sam – makes it much clearer, if you want to prioritize solved in a category.

3 Mi Piace

Maybe @awesomerobot can do some mockups here, I am fine to make solved clearer. I agree that marking something as a solution is not super clear to the OP.

5 Mi Piace

Having "this solved my question below a series of short replies is going to get very noisy very quickly though.

Really need to show mockups of how a topic will look, rather than individual posts.

6 Mi Piace

It’s noisy, but just for OP, so I don’t think it’s so bad. It’s worth a little noise if increases feature use.

I shortened the copy from “this solved my question” to “mark as solution,” the longer version is clearer, but it’s also… long. Using “mark” also gives us “unmark” as the reverse.

Also Font Awesome’s times-square (:negative_squared_cross_mark:) icon is premium-only, and the times-circle is free, so that’s why I’m using circles here.

Mobile’s a little tricky, maybe we show “solution” and then if they expand the controls we hide the text and just show the icon?

6 Mi Piace

Interesting yeah maybe in mobile we suppress text till clicked … on that note, how would “unmarking” the solution work in mobile?

2 Mi Piace

Yeah it’s difficult to keep the same amount of clarity on mobile, the post controls are already crammed. One option could be to move the controls for solved outside of the existing topic nav

5 Mi Piace

How about emphasizing the mark as solution for the current reply only and shift the emphasis as the reader scrolls? Appreciate it’s much more involved but would reduce noise considerably.

2 Mi Piace

It was implemented in:

This is how it looks on desktop:

Can accept / unaccept:


Cannot accept / unaccept:


The same, but for mobile:


7 Mi Piace

La mia prima impressione è che questo lo abbia reso molto rumoroso.

Il fatto che l’etichetta sia così lunga “Segna come soluzione” e che sia più vicina al pulsante Mi piace rispetto al segno di spunta (di 2 pixel :stuck_out_tongue: ) non aiuta molto.

4 Mi Piace

Penso che questo dimostri molto bene la mia preoccupazione precedente.

2 Mi Piace

Cosa succederebbe se sfruttassimo il design della Wiki per mantenerne un modello coerente?

Post normale:

Wiki:

Soluzione:
image

5 Mi Piace

Credo valga la pena rivalutare l’idea di cambiare l’iconografia con questo grande aggiornamento. I cerchi appaiono un po’ meno evidenti nell’elenco. So che c’è una certa resistenza da parte di chi considera queste modifiche come un “trucco da barzelletta”. Tuttavia, vorrei mantenere la forma quadrata, se possibile, anche se dovessimo ridisegnare 1-2 file SVG.

Abbiamo tentato l’unione venerdì scorso, ma l’ho annullata perché avevamo commesso un errore: abbiamo applicato le modifiche allo stile anche ai post non dell’OP (Original Poster). L’intenzione era limitare il cambiamento in modo estremamente preciso esclusivamente all’OP (non allo staff, ad esempio).

Un’altra preoccupazione che ho riguardo all’OP è l’“invito continuo” a “rimuovere la soluzione” una volta che qualcosa è stato contrassegnato come soluzione: trovo che sia un po’ disordinato. C’è qualcosa che possiamo fare al riguardo? Per “rimuovere il cuore” basta cliccare di nuovo sul cuore: perché non seguire lo stesso schema?

4 Mi Piace