IfcBridge element renders invisible / incorrectly with @thatopen/component

[fahgundin]

Describe the bug 📝

When loading an IFC model that contains an IfcBridge element, the element does not render correctly in the viewer. It loads without errors, but is either invisible or displayed incorrectly, unlike other IFC entities in the same model, which render as expected.

I compared the rendering against another BIM software (screenshots attached), where the IfcBridge element is displayed correctly with its expected geometry, confirming the IFC file itself is valid and the geometry data is present.

Reproduction ▶️

No response

Steps to reproduce 🔢

1. Load an IFC model containing an IfcBridge entity using the standard loading flow (FragmentsManager + IFC-to-Fragments conversion).
2. Add the resulting Fragments model to the scene.
3. Observe that the IfcBridge element is missing/invisible or rendered incorrectly, while other entities (e.g. IfcBuilding, IfcSlab, etc.) in the same file render normally.

System Info 💻

System:
    OS: Linux 6.8 Ubuntu 24.04.4 LTS 24.04.4 LTS (Noble Numbat)
    CPU: (6) x64 AMD EPYC Processor (with IBPB)
    Memory: 9.07 GB / 11.68 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 18.19.1 - /usr/bin/node
    npm: 9.2.0 - /usr/bin/npm

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Community.
• The provided reproduction is a minimal reproducible example of the bug.