Skip to content
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

Option to allow Markdown in Project/Activity-comments #677

Closed
ralf1070 opened this issue Apr 4, 2019 · 3 comments · Fixed by #807
Closed

Option to allow Markdown in Project/Activity-comments #677

ralf1070 opened this issue Apr 4, 2019 · 3 comments · Fixed by #807
Milestone

Comments

@ralf1070
Copy link

ralf1070 commented Apr 4, 2019

To be able to better describe projects and activities it would be nice to have an option to activate Markdown in comments of both of this record types. Currently all formating within these comments is ignored, even newlines to at least have paragraphes are skipped.

I read the statement about possible security risks in the documentation. Even if I can't see the risk: it would be nice if this feature could be enabled as an option for installations where security issues are no problem.

@kevinpapst
Copy link
Member

The used Markdown parser does not apply sanitization, so you could potentially insert javascript code, which could again potentially lead to security issues ... always assuming that you can't trust the user.

But yes, feature request accepted.

@kevinpapst
Copy link
Member

Wanna test it? This will be added with #807

@lock
Copy link

lock bot commented Jul 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.

@lock lock bot locked and limited conversation to collaborators Jul 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants