-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KB: Improved Links (OX-11128) #2024
Conversation
OX-11128
First, using the body block (i.e. nested elements) to pass the caption of a link feels more HTML-ish. Second, it is probably not well-defined what the `name` of a link is supposed to be. Therefore, this commit introduces a new attribute `label` that defaults to the rendered content of the element. The old `name` attribute is deprecated and used as fallback only. OX-11128
Links without labels render only as icons with excessive whitespace. This does not look good, does not make much sense, and is probably also not good for screen readers. OX-11128
OX-11128
Like that, we will be able to have reference links in KBAs that follow the flow of the text without resorting to normal links. The new label can be provided either as an attribute, or via the child content of the element. OX-11128
The label is now translated to the user's language, shows an error icon and is rendered in red. In addition, a tooltip provides context information about the error. OX-11128
OX-11128
OX-11128
This whitespace may lead to spaces appearing in front of punctuation characters where it is plainly wrong. OX-11128
Mhhhh I don't know whether I would prefer a more "graceful"/silent failing when the user has no access to the underlying KBA. Wouldn't it be better to just schow the label as plain text instead. Is there any benefit for the user to see that there could have been some link? |
There are several possible scenarios where this question matters:
Considering that scireum editors have privileged access, the error case appears to be of relevant likelihood, and marking the error appears to be prudent such that customers can complain, as they can still tell that there should have been a link. For the first case, equivalent behaviour could be reached via use of (Originally discussed in person during the OX Daily on July 23) |
Description
Improves the
<k:ref>
and<k:link>
tags:<k:ref>
<a>
)name
attribute of<k:link>
is deprecated in favour of this label, due to misleading naming.<k:link>
<k:ref>
Additional Notes
Checklist