Possible to skip rendering of layers (optional content config)?

[laurensschuitemaker]

I have a PDF drawing with a huge amount of paths.
Is it possible to skip the rendering of a selection of these paths, based on the layer they are in?

I've tried to use the 'getOptionalContentConfig()' implementation, by using:
optionalContentConfig.setVisibility(groupIndex, false)

But it seems the paths are still rendered, which freezes the browser.
Is it possible to skip the rendering of these paths altogether, when the path is part of the disabled layer?

I've tested this by counting the amount of executions of the function "constructPath" in the class "CanvasGraphics".

[Snuffleupagus]

I've tried to use the 'getOptionalContentConfig()' implementation, by using: optionalContentConfig.setVisibility(groupIndex, false)

But it seems the paths are still rendered, which freezes the browser.

If you mean that disabled layers still become visible, that would be a bug (assuming that you disabled the layer correctly).

If that's the problem, can you also reproduce it in the demo viewer?
See https://mozilla.github.io/pdf.js/web/viewer.html, where you can load a PDF document using either the "Open File" button in the SecondaryToolbar or by dragging-and-dropping it.

Is it possible to skip the rendering of these paths altogether, when the path is part of the disabled layer?

I've tested this by counting the amount of executions of the function "constructPath" in the class "CanvasGraphics".

If you mean that the disabled layer is indeed invisible, as expected, but that the paths are still parsed then that's intended and necessary behaviour given section 8.11.3.1 of the PDF specification:

When a piece of optional content in a PDF file is determined that it shall be hidden, the following occurs:

• The content shall not be drawn.
• Graphics state operations, such as setting the colour, transformation matrix, and clipping, shall still be
  applied. In addition, graphics state side effects that arise from drawing operators shall be applied; in
  particular, the current text position shall be updated even for text wrapped in optional content. In other
  words, graphics state parameters that persist past the end of a marked-content section shall be the same
  whether the optional content is visible or not.

[laurensschuitemaker]

Thanks for your response.

The layers do not become visible, so that's ok. But the browser freezes completely.

I've also tested it on the demo viewer. In Chrome/Brave it freezes the browser. However, in Safari it works fine with the same file.
Do you have any idea why that is? Or which parameter I could change so it works on Chrome too?

[Snuffleupagus]

I've also tested it on the demo viewer. In Chrome/Brave it freezes the browser. However, in Safari it works fine with the same file.

What about Firefox, since that's our primary development target?

Do you have any idea why that is? Or which parameter I could change so it works on Chrome too?

Unfortunately not, and previously we've seen issues where only Chromium-based browsers crash.

[laurensschuitemaker]

In Firefox it's also working fine, no issues there.
Anything I can do about this in Chrome?