Nested mouseover notes can be entered but not shown

Ahoj,

Discourse can do nested mouseover notes:

Hier ein Text^[eine Mouseover-Note^[eine Mouseover-Mouseover-Note].]

This is rendered as

Hier ein Text[1]

When I go with the mouse on the “[1]”, I get a popup with the text “eine Mouseover-Note[1]”. The “[1]” within that popup is rendered in blue as well, but when I move the mouse on that the information hidden behind it is not shown.

I think this is a usability bug, because it suggests to the writing person that nested mouseover notes work, but in the end one is not able to reach the information behind the nested note.

Suggestions to solve it from a usability perspective:

  • Make it such that nested mouseover notes are actually showing their content, or:

  • Do not allow nesting – so that

    Hier ein Text^[eine Mouseover-Note^[eine Mouseover-Mouseover-Note].]
    

    would be rendered as

    Hier ein Text[2]

    (i.e. the nesting does not create a nested note but the entered code is printed verbatim: Moving the mouse on the outer note reveals a popup with the text “eine Mouseover-Note^[eine Mouseover-Mouseover-Note].”)

Regards!


  1. eine Mouseover-Note[1]. ↩︎

  2. eine Mouseover-Note^[eine Mouseover-Mouseover-Note]. ↩︎

3 Likes

Hello @dreieck and thank you for that well written report.

Unfortunately both your suggestions were not only quite difficult to implement, but also may lead to a box-of-pandora infinite-nesting type situation. In my opinion, nested footnotes are suboptimal UX-wise and should not be allowed.

So I’ve opted for a third route, which is to strip away any nested footnotes.

I know this may not be what you hoped for, but it at least addresses the bug of pretending it works while it doesn’t.

If you’re convinced this functionality is worthwhile having, I’d recommend adding your vote to this existing feature request, asking the same thing.

Ahoj,

to understand:

Why is my second suggestion (to not interpret a nested note but just print verbatim) more a problem than the suggestion in the pull request you linked (strip away any nested notes)?

1 Like

It was technically more difficult to do, and as I said, I do not think it’s good UX to begin with. At that point, why not just put everything in one note if they’ll get pasted together anyway?

OK!,

I was mainly thinking of people who just do that blindly without looking at the rendered result.

3 Likes