-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add option to collapse preformatted blocks, configuration option to set default #174
Comments
@jamestomasino mentioned on IRC that they've not specified the generic fallback, in the case that no alt-text is given. I suggest(ed) that a simple 'missing alt-text' or 'no alt-text provided' message be used. |
I think this feature might be possible, however the only implementation method I can think of (using the current infrastructure) is extremely hacky. (Since kristall works by literally writing to a rich text document and displaying it to the user) My solution would be like follows: say a user has collapsible blocks enabled, Kristall would render the document similar to this (mocked up in GIMP): And then when a user clicks on the KristallTextBrowser widget, send the QTextCursor to that block (using the mouse click position), delete the block, and insert a new block with the preformatted text: I guess the same approach could be used to fold the uncollapsed block too This all seems pretty dodgy but it might work. |
I think this solution isn't that bad actually. We could do that! |
The preformatted text blocks have an alt text property following the three backticks which is designed to be a human-readable representation or indication of what is in the block. This feature gains value for blind users when our clients embrace it and allow it to be displayed instead of the wall of text common in ascii art or even code samples.
Davin Prater's post on the mailing list explains this from the POV of a blind user quite well.
As a feature request I would ask for two additions to Kristall to improve it for blind users:
The text was updated successfully, but these errors were encountered: