FOOTNOTE ... if you opened the Tiddler in edit mode you may get a bit confused in wondering HOW does the rendered version relate to the source tiddler? :-). Its because I am using BJ's Flexity plugin. The transformations are triggered by the Content Type and performed by https://onepager.tv/tw_reggie.html#rx-mason-tids-jason-RT%201. But all that is beside the point in that at the surface end the problem is the same.
Hmm... I know of a few people that might consider "uncopy-able text" a feature. ;)
Thanks! I understand now: because they are css generated they don't exist in the DOM
BurningTreeC wrote:Thanks! I understand now: because they are css generated they don't exist in the DOM
I suspected it might be a DOM-inique issue. Though obviously in this case DOM-inique is hands off.
The WEIRDNESS of the end-result remains for me. That a normal end-user seeing something on-screen they can't simply copy and paste it. That is ridiculous!
My original question was about whether there are ways to copy (surface render) that could include the CSS generated content.
Given that the characters exist on-screen--in my face. It seems bizarre you can't simply copy and paste them.
Surely there must be a way to do that?
1 - If assistive tech can't find it, ARIA is failing.
--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ce5a26d1-3c55-4d23-b3c4-6369f7046ec3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jeremy: This is a common issue, I’m afraid. Here’s one of many StackOverflow answers about it ...
I read around the issue and then discovered that there are proposals in CSS to change the behaviour but they somewhat in conflict with existing DOM approach ... https://drafts.csswg.org/css-ui-4/#content-selection. I haven't tested if any browsers adopted the proposal--the point is that the default setting is "uncopyable" but the proposal is to permit copying using a "user-select" property with several different available settings.
element::before {
user-select: text;
...
}
I just hit a weird issue (to me). I assume its something to do with the DOM-inique thing?
I generate Tiddlers that include CSS generated counters like this ...
BUT when I try to copy-highlight it I get this ...
The copy-highlighter skips the CSS generated number content. And when I paste it the numbers are missing.
I looked at the generated HTML and there also the CSS generated numbers are missing. B*mmer.
I guess its not a TW issue so much as a broader issue with DOM-inique?
BUT its a PITA because I'd dearly like to use CSS to generate lots of indices to help construct tiddler structures like the above.
MY QUESTION for the truly savvy: Is there ANY way I can get to copy the final surface render that includes the CSS generated numbers?
In hope
Josiah
I'm not sure if I've understood correctly, but, that draft seems to suggest that in Firefox you may be able to set user-select, either in the parent element or in the before/after pseudo element itself:
I'm not familiar with how your regex tools work. Do they re-iterate until there are no more changes to be made?
If so, then I'm thinking that rules like this at the very end:
/(.*?)#startmarker#/$1 0001#endmarker#/
/(.*?)#startmarker#/$1 0002#endmarker#/
.... etc.
Might brute force what you want.
What I'm suggesting is that you don't need the counters -- you create a 1000 rules to apply a 1000 counts, one after the other. Building up those rules shouldn't take long in a good text editor (especially one's like Emacs that have column modes).