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

Better error name copy-paste #119

Open
mukrop opened this issue Oct 14, 2021 · 4 comments
Open

Better error name copy-paste #119

mukrop opened this issue Oct 14, 2021 · 4 comments
Labels
enhancement New feature or request up for grabs Issues open for any contributors

Comments

@mukrop
Copy link
Member

mukrop commented Oct 14, 2021

Use the accessibility options to copy error name without hyphens?

@mukrop mukrop added enhancement New feature or request up for grabs Issues open for any contributors labels Oct 14, 2021
@leonspohr
Copy link

Could you please provide more informations, so that I can start working on this issue?

@mukrop
Copy link
Member Author

mukrop commented Oct 15, 2021

Hi,
Although the up for grabs label was more meant for anyone in the team, I'm open to external collaborators :-). (That explains why the description was rather brief, more of a note-to-self).

The issue is as follows: To provide a good mobile browsing experience (https://x509errors.org/), all "error block names" have discretionary hyphens after each underscore to wrap nicely on narrow screens. However, when copy-pasting the error code from the website, this is rather impractical (you don't get the error code but the error code with extra hyphens).

This issue needs someone to investigate if there is a better option (retaining the wrapping on narrow screens yet having the correct string copied). Someone told me there may be a way to set a different string to be copied via some HTML accessibility options (though I have never used such a feature before).

So, if you feel like it, do investigate and let me know here if you find a viable solution :-).

@leonspohr
Copy link

Ok, I would really like to look into this issue, but I don't really know, where to start. Could you at least tell me, in which HTML file this occurs?

@mukrop
Copy link
Member Author

mukrop commented Oct 17, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request up for grabs Issues open for any contributors
Projects
None yet
Development

No branches or pull requests

2 participants