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

Reconsider presenting links in responses in "reference-style" #4578

Closed
RichardTaylor opened this issue Mar 22, 2018 · 3 comments
Closed

Reconsider presenting links in responses in "reference-style" #4578

RichardTaylor opened this issue Mar 22, 2018 · 3 comments
Labels
f:request-management improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) stale Issues with no activity for 12 months user-experience x:uk

Comments

@RichardTaylor
Copy link

Alaveteli currently presents some incoming messages in a format where links (email links and web links) are extracted and displayed below the text.

This often surprises and confuses users.

Should Alaveteli display the plain text version rather than try to reformat a HTML version of an incoming mail?
Should Alaveteli display links in-line when presenting a HTML version of an incoming mail.

Suggesting this as an alternative to fixing #4577 (Reference-style links get hidden in the quoted section).

@RichardTaylor
Copy link
Author

Just to link to the other major HTML rendering issue:

#1528 (Improve/fix HTML rendering of tables)

@garethrees garethrees added f:request-management improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) labels May 29, 2018
@garethrees garethrees changed the title Reconsider presenting responses in "reference-style" Reconsider presenting links in responses in "reference-style" May 23, 2022
@WilliamWDTK
Copy link
Collaborator

This has recently caused some confusion with a request for some rather aesthetically-pleasing Victorian engineering drawings for Branksome station. Network Rail (NR) shared some files through SharePoint/Onedrive because they were large, there was an automated email with an authenticated link (with an access token), but their subsequent manual email included a direct link to the file, which required a NR log-in to use. This could perhaps have been avoided had the links in the automated email been easier to see.

Note that the fault here is partially with NR for sending a link manually which couldn't be used.

@HelenWDTK
Copy link
Contributor

This issue has been automatically closed due to a lack of discussion or resolution for over 12 months.
Should we decide to revisit this issue in the future, it can be reopened.

@HelenWDTK HelenWDTK closed this as not planned Won't fix, can't repro, duplicate, stale Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
f:request-management improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) stale Issues with no activity for 12 months user-experience x:uk
Projects
None yet
Development

No branches or pull requests

4 participants