Add a copyable link of the PDF file location in the macro toolbar #40

[trrenty]

• Clone a button from each toolbar and modify it with the proper data
• Bundle a new image for the copy button in the webjar module
• Through maven, modify the viewer.css file to add a new style for the added buttons to display the aforementioned image
• Add the event listeners for the buttons in JavaScriptExtension
• Update the pom of the ui module to have requirejs and jquery as dependencies

In the previous example, the clipboard was populated with: http://localhost:8080/xwiki/bin/download/PdfTest/WebHome/helloworld.pdf?rev=1.1

This issue had me modify many files:

• The buttons were cloned in the pdfviewer-customizations.js that is included in the viewer.html, so the changes come as soon as the iframe contents are loaded
• viewer.css file was modified in the pom of the webjar module because styling pseudoelements in JS would have complicated things
• The event listeners were added in a newly created JavaScriptExtension because I needed to add localized text to the buttons and use the XWiki notifications system

Note: I used URLSearchParams, a feature that is not supported on IE, because pdf.js is already using it. They dropped support for non-chromium IE since 2.6.347. Since the commit on PDF Macro that pulled pdf.js through a webjar, we are using 2.9.359.

[mflorea]

Note: I used URLSearchParams, a feature that is not supported on IE, because pdf.js is already using it. They dropped support for non-chromium IE since 2.6.347. Since the commit on PDF Macro that pulled pdf.js through a webjar, we are using 2.9.359.

They mention that we can use the -es5-dist.zip package if we need to support IE11, so we should try that (if it's not too complex). The fact is that IE11 support has been dropped only in XWiki 14.0 and we still need to support XWiki 11.10+ so we still need to support IE11. If we want to make an exception for the PDF Viewer macro we need to ask the support (and client teams) about this. It's not our decision.