1. User - set colors should not be overwritten
2. The default color should be set directly at model initialization（can avoid overwriting custom colors）

 new BpmnModeler({
      bpmnRenderer: {
        defaultFillColor: '#17171a',
        defaultStrokeColor: '#FFF',
      },
    });

It works great for BPMN diagrams, but not really for DMN.

Regards,
A.

(moved from camunda/camunda-modeler-plugins#108)

Describe the Bug

When I edit a BPMN model with the Dracula plugin installed, it changes the color of all labels from:

<bpmndi:BPMNLabel>

to:

<bpmndi:BPMNLabel color:color="rgb(207, 205, 205)">

Steps to Reproduce

1. install Dracula plugin
2. open the Modeller
3. open a BPMN
4. change something
5. save
6. examine the updated BPMN

Expected Behavior

It should never change the color in the BPMN.

Environment

• OS: MacOS 14.4.1
• Camunda Modeler Version: 5.21.0

DMM elements is also not completely themed.
Is this just me?

Example in screenshot below the input search text is "Even" but it not readable due to white on white.

Using Windows 10
Attempting to label any element causes an error and the label won't show up, though the text is still there when you re-edit.

I Changed DraculaTheme.js line 13 'label' to 'bpmnElement', so from:

element.di.label.set('color', element.di['border-color']=getComputedStyle(document.documentElement).getPropertyValue('--color-grey-225-10-35'));

To:

element.di.bpmnElement.set('color', element.di['border-color']=getComputedStyle(document.documentElement).getPropertyValue('--color-grey-225-10-35'));

and it seems to work now, but I don't understand it enough to do a PR.

log.txt