This is a common issue, I’m afraid. Here’s one of many StackOverflow answers about it:
https://stackoverflow.com/questions/24385171/is-it-possible-to-select-css-generated-content <https://stackoverflow.com/questions/24385171/is-it-possible-to-select-css-generated-content> Best wishes Jeremy. > On 19 Feb 2018, at 20:17, whatever <[email protected]> wrote: > > Well, considering the source is a JSON-y array, cobbling up something in JS > should be pretty simple. > w > > On Monday, February 19, 2018 at 8:24:28 PM UTC+1, coda coder wrote: > > > On Monday, February 19, 2018 at 12:26:08 PM UTC-6, @TiddlyTweeter wrote: > 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. > > > I have no idea what that is. The problem is as I've (we've) already > described. It's CSS, not HTML, it's not in the DOM and hence "it's not > there". > > 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! > > > And terrible. I'm now filing after/before under DO NOT USE. I suspect these > folks may have something to say on the matter, too: > > https://groups.google.com/forum/#!forum/free-aria > <https://groups.google.com/forum/#!forum/free-aria> > > 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. > > > And that's where I think you have a case for filing a category-1 bug. > > 1 - If assistive tech can't find it, ARIA is failing. In the words of Donald > Trump, that's sad. > > 2 - If Ctrl-F can't find it, search is broken. > > 3 - If it can't be read back from the screen, you can't write a test. If you > can't test, you can't validate your code. End of discussion. Hence, DO NOT > USE. > > > Surely there must be a way to do that? > > > Nope. There is no JS solution I know of, anywhere. Any thoughts I have are > immediately stymied by "it's not in the DOM". I can wildly imagine someone > coding up a pseudo-dom AST that then renders to a real DOM element but > really... it's not worth the effort. > > > > > -- > 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 [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywiki > <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 > > <https://groups.google.com/d/msgid/tiddlywiki/ce5a26d1-3c55-4d23-b3c4-6369f7046ec3%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CC65CC66-4664-495E-A234-325A8E4F49BD%40gmail.com. For more options, visit https://groups.google.com/d/optout.
