References don't work and make all text containing a slash / to be treated as a reference

[agamez]

On version 0.8.3, having ingredients lists such as "1/2 kg of tomatoes", now appears as "1undefined2kg of tomatoes".

Entering a properly formatted reference as, for example, #r/2540402 (real ID of a recipe of mine) results in the recipe viewer as appearing
"<a class="recipe-reference-inline" href="undefinednextcloudundefinedindex.phpundefinedappsundefinedcookbookundefined#undefinedrecipeundefined2540402">#2540402<undefineda> "

Also, the popup with the list of references appears not only when writing #, but also when entering a 3 in which # character is located too (but not with the numeric keyboard).

Main problem, however, is it treating every / occurance as a reference to undefined, as this is breaking already existing functionality.

[seyfeb]

To make sure I understand you correctly: Whenever you press the button for entering a '3', the recipe-selection pop-up opens?

Otherwise duplicate of #641

[agamez]

That is correct. Typing a 3 (key above 'e') launches the pop-up. Typing a 3 (on the numeric keyboard above '.' and to the left of Intro) does not launch the pop-up.

Please, review my original message which I've editted to properly show that there appears HTML output on recipe view, so it's not only the / -> undefined of #641, but also spurious HTML appearing out of nowhere.

Thanks!

[christianlupus]

This is due to the check for keycode in the EditInputField.vue file.

I am not sure if the keycode approach is so well suited. The hash has only keycode 51 on the US keyboard. Other layouts have the hash on different keys with different keycodes. On the German (for example) it is 163, while 51 is 3/§.
Wouldn't it be more feasible to let the browser type the symbol and later check the textual representation of the lastly typed glyph?

[seyfeb]

I see! This should definitely be changed to work on any keyboard layout.

[seyfeb]

This can be closed if #648 and #642 solved the problems.

[christianlupus]

I am closing here as the PRs should have taken care of the issue.

If the problem still persists, we can reopen.