Page Editor » Specify Target Attribute for External Weblinks

1 Initial Problem

With the removal of HTML/JS in the ILIAS page editor we are no longer able to specify the desired behaviour for external weblinks. Before we could use "<a href="https://docu.ilias.de" target="_self">mylink</a>" to tell the the clients browser to open the link in the same tab/window (note: this can still be overwritten by the enduser, but 99,9% of people don't). Now all external weblinks are always created with target="_blank" which means that they are opened in a new tab/browser window by default 99,9% of the time.

2 Conceptual Summary

The page editor should offer the user to specifiy the link target when an external link is created by adding the target attribute. I.e.:

"[xln url="https://" target="_blank"][/xln]" or "[xln url="https://" target="_self"][/xln]

Users should be able to specify the target attribute:

• _self - Default. Opens the document in the same window/tab as it was clicked
• _blank - Opens the document in a new window or tab
• _parent - Opens the document in the parent frame
• _top - Opens the document in the full body of the window

3 User Interface Modifications

3.1 List of Affected Views

• none

3.2 User Interface Details

None, the attribute can be added to the link in the text paragraph.

3.3 New User Interface Concepts

None, users can just change the target attribute for the external link. Same as they have to enter the url property.

3.4 Accessibility Implications

None.

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Sesterhenn, Fabian [sesterhenn]
  
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• TH Köln

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.