Following on from motivations ... the background story starts.
Some while ago I added a copy button to a website I use (maintain and am developing). The goal was to copy an HTML element, specifically a table of tables of unspecified dimension, generally small but conceivably large, to the clipboard for use in emails.
The legacy solution π΄: Select and Copy
When first researching the options I implemented a simple solution published by R Brewer on Stack Overflow.
It uses document.createRange
and Range.selectNodeContents()
for selecting an HTML element, and then document.execCommand('copy')
to copy it to the clipboard.
The full solution paraphrased a little and reproduced here is:
function copyElementToClipboard(el) {
var body = document.body, range, sel;
if (document.createRange && window.getSelection) {
range = document.createRange();
sel = window.getSelection();
sel.removeAllRanges();
try {
range.selectNodeContents(el);
sel.addRange(range);
} catch (e) {
range.selectNode(el);
sel.addRange(range);
}
} else if (body.createTextRange) {
range = body.createTextRange();
range.moveToElementText(el);
range.select();
}
document.execCommand("Copy");
}
That sort of works ... well enough, so I stuck with it for a fair time.
The legacy problems: It ain't all roses ... πΉπΉ
This solution has a number of problems in practice. They were all tolerable for some while or have fixes or workarounds, but they are problems all the same:
Firefox loses much of the styling in the process. Specifically and noticeably to me, the colours of the table rows. All colours are lost. Chromium in contrast honours them and preserves colour in the copy. The workaround here was fine, just used Chromium or Chrome to prepare emails. And all was good.
The selection is visible. That was so clumsy and ugly that it had to go. The fix is not hard, basically the the element is copied, and then moved off-screen and that element selected, so it's not visible when the selection happens. A neat trick. The implemented solution looked like so:
function selectElementContents(el) {
let body = document.body, range, sel;
if (document.createRange && window.getSelection) {
range = document.createRange();
sel = window.getSelection();
sel.removeAllRanges();
try {
range.selectNodeContents(el);
sel.addRange(range);
} catch (e) {
range.selectNode(el);
sel.addRange(range);
}
} else if (body.createTextRange) {
range = body.createTextRange();
range.moveToElementText(el);
range.select();
}
}
function copyElementToClipboard(element) {
let el = element.cloneNode(true);
el.setAttribute('readonly', '');
el.style = {position: 'absolute', left: '-9999px'};
document.body.appendChild(el);
selectElementContents(el);
document.execCommand('copy');
document.body.removeChild(el);
}
This carried one caveat, and it made me cringe and laugh at the same time. Firefox, actually respected the positioning style and chromium did not. A complete reversal of their behavioral idiosyncrasies. What that meant was Chromium copies still worked fine, but Firefox copies, not only lost all colours, but were positioned way off to the left of the page and pasted into an email it was not visible (unless I looked at the HTML source of email - necessary to see what's going on).
No problem I thought. I just wrapped it in a div
, that was positioned, then I copied the element inside the div
, not the div
itself. But Firefox was just too smart for me, and still positioned the table off-screen to the left when pasted (inherited position of course, from the wrapping div
). Never mind, Chromium worked fine.
And that then, was the working solution for a long time. I just used Chromium to copy these tables.
The legacy broken: One straw too many ... πͺ
Then one day, I wanted finally to simplify and centralise the colour management on the site, so I sucked out all the CSS colour style values into CSS variables. And suddenly the colours all disappeared from my Chromium copies as well.
And so commenced the hunt for a fix. How, oh how, to fix this? Alongside the desire to support CSS variables was the desire to lose the selection trick, and do something a little less hackish and more slick.
Step 1 would be survey the options tor getting data onto the clipboard.
Top comments (0)