Issues with the Chrome based Root Browser

ROOT
1

Two small issues to report.

The chrome based browser displays latex strings such as #bar{p} correctly as anti-proton (p-bar) but once they are printed to PDF, the “bar” disappears and the “p” is too high. But I verified that the bar is properly placed when writing a jpg file.

The chrome based browser event bar status reports data incorrectly. When I overlay several histograms and hover the mouse on one point, I get the value of the last histogram plotted, not the point I am hovering the mouse onto.

Thank you

Claude

ROOT Version: 6.36.02
Platform: macosx64
Compiler: Apple clang version 17.0.0 (clang-1700.6.3.2)

2

I think @linev can help you with these two small issues.

3

Hi Claude,

PDF output can have such issues while we start use jsPDF.js to create it - and it may fail.
When run with chrome browser, one can use screenshot functionality like:

c1->SaveAs("c1.screenshot.pdf");

In such case native chrome PDF conversion is used - which should work properly.

And with second issue - try also enable “Tooltip info” to see how mouse interaction with histograms
are working. While tooltip info used also to show event status - even when tooltip is not displayed.
For instance, when mouse cursor higher than histogram - than no tooltip shown.
If there are several histograms - histogram selection is more tricky. So just try to see how tooltip is working.

Regards,
Sergey

4

Thanks Sergey

I will give your suggestions a try. :slight_smile:

Claude

5

Hello again.

The tooltip tool works fine. Thanks!!! I will use that in the future…

However, Using c1->SaveAs(“xxxx.pdf”) does not produce the desired result (on my MAC)– although it is faster.

CP

6

Did you start root with root --web=chrome?

7

And to use chrome functionality you should use filename with screenshot inside like:

c1->SaveAs(“xxxx.screenshot.pdf”)
8

Hello Sergey

Thanks for your latest suggestion. I get the following issue when I explicitly include “screenshot” in the filename to be produce.

Error in <[ROOT.WebGUI] Error /private/tmp/root-20250709-17667-z18rbs/root-6.36.02/gui/webdisplay/src/RWebDisplayHandle.cxx:1404 in static bool ROOT::RWebDisplayHandle::ProduceImages(const std::vectorstd::string &, const std::vectorstd::string &, const std::vector &, const std::vector &, const char *)>: Fail to produce image /Users/aa7526/Documents/MyPublications/Theory/BalanceFunctions/FeedDownHadronGas/New/ThermalDensityVsTempVsIndex.screenshot.pdf

Error in <[ROOT.WebGUI] Error /private/tmp/root-20250709-17667-z18rbs/root-6.36.02/gui/webdisplay/src/RWebDisplayHandle.cxx:1404 in static bool ROOT::RWebDisplayHandle::ProduceImages(const std::vectorstd::string &, const std::vectorstd::string &, const std::vector &, const std::vector &, const char *)>: Fail to produce image /Users/aa7526/Documents/MyPublications/Theory/BalanceFunctions/FeedDownHadronGas/New/ThermalDensityVsTempVsMass.screenshot.pdf

9

Did you run with --web=chrome arguments?

10

Yes. I did. I don’t get the errors with just –web… My guess is that has to do with the MacOS platform being difficult…. C

11

For me chrome on the MacOS works perfectly.
Did you have it installed on your system?
Please check $ROOTSYS/etc/system.rootrc, I have following entries there:

WebGui.Chrome:             /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
WebGui.ChromeVersion:

For the moment chrome is the only possibility to use native browser renderer for creation of PDF files. Unfortunately jsPDF.js has several such problems, but it works on all platforms.

12

I checked that file on my installation of root. It contains the correct line - same as yours…

That’s OK. I will use jpg format.

Thanks for your help!

Claude

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.